CDK server adapter, connection: update registry url in all connections that exist (not just 1)

1. ASSERT: have 2 connections to the same cdk instance (ex. one for admin, another one for developer)
2. ASSERT: make sure both *DONT* have a registry url (it's in the connection wizard, under the Advanced >> section)
3. ASSERT: have a CDK server adapter that is *STOPPED*
4. EXEC: start the CDK server adapter

Result:
Once the adapter is started, only 1 connection gets updated (ex. the connection for developer) with the registry url of the registry within the cdk. The other one (ex. the one for admin) isn't.