Separate client and runtime connections (contributes to #776)

[sstone1]

The work for #776 requires that the runtime connection and runtime ops view works very differently to how it works today, so the time has come to split client and runtime connections apart.

This is the first stage of the changes where we simply separate the interfaces and make sure the right code is using the right one. Further changes will come where the methods on each interface are cut down, and common code moved into the right place.

• Split IFabricConnection into IFabricClientConnection and IFabricRuntimeConnection
• Gateway tasks (submit, evaluate, generate tests, etc) use IFabricClientConnection
• Ops tasks (install, instantiate, upgrade, etc) use IFabricRuntimeConnection
• Update the connect command to always use IFabricClientConnection, even when connecting to the local Fabric

I started off with this change, then found that we need to do this and backed it out:

• Update the create identity command to use the runtime managers connection object, not create its own each time

This is because we have to switch to the admin identity, instead of the Admin@org1.example.com identity, in order to perform CA operations. Will remove that later when the admin identity can be used everywhere!

Signed-off-by: Simon Stone sstone1@uk.ibm.com

[cazfletch]

LGTM