Connector routing should be automatic

[swgraham]

Any 'Service' Added by the service as a response to the service query should support a 'topic' (that is a string) and a 'schemes' topic that is an array of strings. This list of strings in the scheme topic will define the prefix that can be added to an endpoint and force a start_ession to that service topic

[swgraham]

Problem was with the presumed name of the service. Removed name dependency. We find the route based on what schemes are present on a service. First one found, is the first one returned. The Service Topic Name (previously SIP_CONNECTOR_SERVICE) doesnt' matter. Updated tests to check this.