Include client and server uuid keys duplicity for TAPI ConnectivityServices

[arthurMll]

After the resolution of issue #340, the agreement has been to consider the posibility of including a second identifier element named server_uuid or similar which is only editable by the TAPI server once the resource is created by a TAPI client based on a client-defined uuid identifier.

The group is open to proposals from TAPI server providers which combine current approach of accepting tapi-client defined uuids as resources keys with a second tapi-server defined identifier which allows them a better management of the resources.

The target for this enhancement would be the next TAPI release after 2.2