Add support for azure deployment creation

[pritt20]

Description

As we have changed the default cloud provider to Azure for deployments on standard cluster. We would also like to have same behaviour on Astro-cli end. Currently, we have default cloud-provider set to gcp in Astro-cli. As part of this PR changes, we are updating default cloud-provider to azure to be in sync with UI.

🎟 Issue(s)

closes #1707

🧪 Functional Testing

Tested the changes by creating default deployment on PR-preview environment using Astro-CLI build with these changes:

./astro deployment create
                                                                         
Current Workspace: Sample Workspace 2

Please specify a name for your Deployment

Deployment name: test-cli

Please select a Region for your Deployment:
 #     REGION         
 1     eastus2        
 2     westeurope     
 3     westus2        

> 2
 NAME         NAMESPACE                     CLUSTER     CLOUD PROVIDER     REGION         DEPLOYMENT ID                 RUNTIME VERSION                      DAG DEPLOY ENABLED     CI-CD ENFORCEMENT     DEPLOYMENT TYPE     
 test-cli     asteroidal-telemetry-9312     N/A         AZURE              westeurope     cm0zkgbag00a401nhf2is3wus     12.1.0 (based on Airflow 2.10.1)     true                   false                 STANDARD            

 Successfully created Deployment: test-cli
 Deployment can be accessed at the following URLs 

 Deployment Dashboard: cloud.astronomer-dev.io/cm0wad7pq0108f7j2he7990qn/deployments/cm0zkgbag00a401nhf2is3wus/overview
 Airflow Dashboard: sampleorgpr23859-pr23859.astronomer-dev.run/d2is3wus?orgId=org_TpYkP1OnRzcNzN8r

📸 Screenshots

📋 Checklist

• Rebased from the main (or release if patching) branch (before testing)
• Ran make test before taking out of draft
• Ran make lint before taking out of draft
• Added/updated applicable tests
• Tested against Astro-API (if necessary).
• Tested against Houston-API and Astronomer (if necessary).
• Communicated to/tagged owners of respective clients potentially impacted by these changes.
• Updated any related documentation

[neel-astro]

left a minor comments, but thanks for making the change 🚀

[neel-astro]

LGTM

[schnie]

@pritt20 @neel-astro as discussed in the PLG slack channel thread, we probably want to document this as a breaking change since it has the potential to cause a change in behavior. cc @chomipi88