Explore deployment service and management API and configuration store options about azuretre

[jjcollinge]

A few other requirements:

• Must support a mechanism to expose the deployment outputs back to the management API. Or atleast support a method for reading them from another source from the management API.
• Must support a mechanism to handle secrets securely i.e. return secret references rather than the secret in plaintext.
• Must provide a feedback mechanism for seeing the progress and status of async operations.
• Must not drop operations - all operations should finalize (Succeed or Fail).
• Must try to finalize to a state that is consistent with the APIs view of the world.
• Must support operations (create, update, delete) on resources concurrently.
• Must be resilient to component failures (inc. API throttling).
• Must support referencing dependent resource operation output data.
• Must scale to support *many services within a workspace.

I'll probably add a few more as I think about them.

[TessFerrandez]

Decision was made that at a high level we will re-use a lot of the design from an internal engagement by the Clarke team - but remove dependencies on CAF and moving to python where possible