fix: update VM size defaults and enhance troubleshooting documentation for the same

[Harsh-Microsoft]

Purpose

This pull request updates the default jumpbox VM size for deployments to use a more modern and broadly available SKU (Standard_D2s_v5) instead of the legacy Standard_DS2_v2. It also introduces a new environment parameter for customizing the VM size, improves documentation and troubleshooting guidance for VM sizing and related errors, and clarifies which VM sizes are suitable for accelerated networking.

Jumpbox VM default and customization improvements:

• Changed the default jumpbox VM size in infra/main.bicep and infra/main.json from Standard_DS2_v2 to Standard_D2s_v5, ensuring deployments use a current-generation VM with better regional availability and performance. [1] [2]
• Added the AZURE_ENV_VM_SIZE parameter to docs/CustomizingAzdParameters.md, infra/main.waf.parameters.json, and deployment templates, allowing users to easily override the default jumpbox VM size via environment settings. [1] [2]

Documentation and troubleshooting enhancements:

• Updated troubleshooting steps in docs/TroubleShootingSteps.md for SkuNotAvailable and VMSizeIsNotPermittedToEnableAcceleratedNetworking errors, providing region-specific guidance, recommended VM alternatives, and explicit instructions for using and overriding the jumpbox VM size. [1] [2]
• Improved VM size notes in infra/modules/virtualNetwork.bicep to recommend modern D-series SKUs (v5/v4), clarify legacy SKU status, and warn against A-series and B-series VMs for jumpbox deployments.

Template and dependency fixes:

• Corrected the order of DNS zone dependencies in infra/main.json to ensure proper deployment sequencing.
• Updated the Bicep template hash in infra/main.json to reflect the new template changes.

Does this introduce a breaking change?

• Yes
• No

Golden Path Validation

• I have tested the primary workflows (the "golden path") to ensure they function correctly without errors.

Deployment Validation

• I have validated the deployment process successfully and all services are running as expected with this change.

What to Check

Verify that the following are valid

• ...

Other Information