Add Azure Virtual Machines operators, sensor, and trigger (#49796)

[nailo2c]

closes: #49796

Why

This request is from issue #49796. ec2 and gce support these features, so I think it would be great if Azure Virtual Machines also supported them.

How

Implemented hooks, operators, sensors, and triggers following the same pattern as the ec2 provider, with deferrable mode support.

The whole process is shown in sequence diagram below:

sequenceDiagram
    participant DAG as DAG
    participant StartOp as StartOperator
    participant Sensor as StateSensor
    participant Trigger as StateTrigger
    participant Hook as AzureComputeHook
    participant Azure as Azure Compute API

    DAG->>StartOp: execute()
    StartOp->>Hook: start_instance(resource_group, vm_name)
    Hook->>Azure: begin_start(...)
    Hook->>Azure: poller.result() (when wait_for_completion=True)
    StartOp-->>DAG: success

    DAG->>Sensor: execute()
    Sensor->>Hook: poke() -> get_power_state()
    Hook->>Azure: instance_view(...)

    alt state already reached
        Sensor-->>DAG: success
    else state not reached + deferrable=True
        Sensor-->>Trigger: defer(trigger=AzureVirtualMachineStateTrigger)
        loop poll until target state
            Trigger->>Hook: async_get_power_state() [native async]
            Hook->>Azure: instance_view(...)
        end
        Trigger-->>Sensor: TriggerEvent(status=success)
        Sensor-->>DAG: execute_complete()
    end

Loading

What

System Test

1. I prepared Azure cloud resources and DAGs from my local Airflow environment.
   
   
   
2. Starting
   
   
   
3. Running
   
   
   
4. Restarting
   
   
   
5. Deallocating
   
   
   
6. Stopped
   

Doc

---

Was generative AI tooling used to co-author this PR?

• Yes (please specify the tool below)
  Claude ( I've thoroughly reviewed all AI-generated code :) )

---

• Read the Pull Request Guidelines for more information. Note: commit author/co-author name and email in commits become permanently public when merged.
• For fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
• When adding dependency, check compliance with the ASF 3rd Party License Policy.
• For significant user-facing changes create newsfragment: {pr_number}.significant.rst or {issue_number}.significant.rst, in airflow-core/newsfragments.

[dabla]

Really nice and clean code, great work!

[nailo2c]

Hi, thanks for the review, I learned a lot from it! 😄
If there's anything else I should improve, pleas let me know.