fix: update VM size to Standard_D2s_v5 and update related documentation

[Harsh-Microsoft]

Purpose

This pull request updates the default Jumpbox Virtual Machine (VM) size across the deployment to use Standard_D2s_v5 instead of the older Standard_DS2_v2. It also improves documentation and error handling related to VM sizing and availability, making it easier for users to customize and troubleshoot deployments.

Default VM size update and parameterization:

• Changed the default Jumpbox VM size to Standard_D2s_v5 in infra/main.bicep, infra/main.json, and the jumpbox VM module instantiation. This provides better performance and network bandwidth by default. [1] [2] [3] [4]
• Added AZURE_ENV_VM_SIZE as a configurable environment parameter in documentation and parameter files, allowing users to override the default VM size easily. [1] [2]

Documentation and troubleshooting improvements:

• Enhanced the troubleshooting guide for the "SkuNotAvailable" error, with specific instructions and recommended alternative VM sizes if Standard_D2s_v5 is unavailable in a given region.
• Updated VM size notes in infra/modules/virtualNetwork.bicep to recommend Standard_D2s_v5 and clarify the generational differences and availability of supported VM sizes.

Infrastructure template maintenance:

• Updated Bicep-generated template metadata and hashes to reflect the new Bicep compiler version and template changes. [1] [2] [3]

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