Split Calamari Azure functionality into separate package

[MJRichardson]

Azure support (in particular the Azure PowerShell DLL's) add a significant amount of size to the Calamari package.
The worst part is, this extra luggage needs to be pushed to all Tentacles (and other target types), but is only ever used locally on the Octopus Deploy server (all Azure integration happens from the server in 3.0+).

To address this, Azure integration is being split into an Calamari.Azure package, which won't be pushed to remote targets.

[michaelnoonan]

Release Note: Reduced the size of Calamari by splitting the Azure functionality into a separate Calamari.Azure package

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. If you think you've found a related issue, please contact our support team so we can triage your issue, and make sure it's handled appropriately.