Support multiple client types for base implementations

[harjain99]

Support multiple clients for base azure resource, credentials and finder implementations.

The base azure implementations (AzureResource, AzureFinder and AzureCredentials) currently only support a single client type (AzureResourceManager).
With the introduction of a new client type (CommunicationManager) we need a way to generalize extending the AzureResource and AzureFinder models, which can support multiple clients (See gyro-aws-provider).

This PR:

• Updates every createClient call to specify the client class (similar to gyro-aws-provider)
• Provides a generic way of creating clients and extending the Finder implementation where you can specify the client type that resource will depend on.

[tloisel1]

This touches a lot of files, which is not bad in itself.

What we need is an explanation of the problem, the strategy of the solution, and the implementation details of that solution.

In other words, we need an explanation that somebody without in depth knowledge of the code base can understand, and give context to the code changes.

[harjain99]

Update the description @tloisel1