feat(new): Added Azure.ASE.AvailabilityZone

[BenjaminEngeset]

PR Summary

Fixes #2964

Added Azure.ASE.AvailabilityZone.

PR Checklist

• [x] PR has a meaningful title
• [x] Summarized changes
• [x] Change is not breaking
• [x] This PR is ready to merge and is not Work in Progress
• Rule changes
  • [x] Unit tests created/ updated
  • [x] Rule documentation created/ updated
  • [x] Link to a filed issue
  • [x] Change log has been updated with change under unreleased section
• Other code changes
  • [ ] Unit tests created/ updated
  • [ ] Link to a filed issue
  • [ ] Change log has been updated with change under unreleased section

[BenjaminEngeset]

Ready for review @BernieWhite.

I had to do some deployments to test this out.

When enabling it at environment level, all deployed plans within the environments will have the property set to true.

Setting zone redundancy at the App Service Environment (ASE) level ensures that all VMs pre-provisioned for the environment are distributed across different availability zones. The minimum configuration will be 3 VMs by default.

Since it's also inherited on the plan level, the minimum 3 default instances will be distributed across these VMs. Instance 1 on VM1 (AZ1), instance 2 on VM2 (AZ2), instance 3 on VM3 (AZ3) etc.

[BenjaminEngeset]

Thanks @BernieWhite. I agree with you, the custom reason is confusing. I have adjusted accordingly now.