fix: VM size updates, private endpoint refactoring, documentation updates

[Prekshith-Microsoft]

Purpose

• ...

Does this introduce a breaking change?

• Yes
• No
  This pull request updates the default jumpbox VM size to a more modern and widely available SKU (Standard_D2s_v5), improves documentation and troubleshooting guidance for VM sizing and networking, and refactors private endpoint creation for AI services to use explicit modules for clarity and maintainability.

Jumpbox VM Size Default and Documentation Updates:

• Changed the default jumpbox VM size from Standard_DS2_v2 to Standard_D2s_v5 in infra/main.bicep, with corresponding documentation updates to recommend newer SKUs and clarify which VM sizes support accelerated networking. [1] [2] [3]
• Updated parameter names in infra/main.waf.parameters.json and added support for overriding the VM size using the AZURE_ENV_VM_SIZE environment variable.

Troubleshooting and Error Guidance Improvements:

• Expanded troubleshooting documentation to include detailed guidance for SKU availability errors, accelerated networking requirements, and best practices for VM size selection. This includes explicit instructions for checking SKU availability and recommended alternatives. [1] [2]

AI Services Private Networking Refactor:

• Refactored private endpoint creation for AI Foundry and Content Understanding services in infra/main.bicep to use explicit private-endpoint modules, improving clarity and aligning with best practices for private networking. [1] [2] [3] [4]

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