chore: Dev to Main merge

[Shreyas-Microsoft]

Purpose

This pull request introduces several important updates across the infrastructure, documentation, backend, and frontend. The main focus is updating the default VM size for the jumpbox to a newer generation, improving documentation and troubleshooting guidance, and updating dependencies for improved compatibility and security.

Infrastructure and Deployment Updates:

• Updated the default VM size for the jumpbox virtual machine from Standard_DS2_v2 to Standard_D2s_v5 in Bicep modules, ARM templates, and parameter files for both standard and custom deployments, reflecting a move to a newer, more widely available, and cost-effective VM generation. [1] [2] [3] [4]
• Added the AZURE_ENV_VM_SIZE parameter to documentation and parameter files, allowing users to override the default VM size as needed. [1] [2]
• Updated comments and recommendations in virtualNetwork.bicep to reflect the new default and provide clear guidance on VM size selection.

Documentation Improvements:

• Enhanced troubleshooting documentation for the "SkuNotAvailable" error to explicitly reference the new default VM size and provide actionable resolution steps and recommended alternatives.

Frontend Dependency Updates:

• Upgraded several frontend dependencies (minimatch, flatted, glob, brace-expansion, balanced-match) to the latest versions for improved Node.js compatibility and to address security advisories. [1] [2] [3] [4] [5] [6] [7]
• Updated package.json overrides to pin new dependency versions.

Backend and Build Updates:

• Added gawk to the backend and processor Dockerfiles to support scripts or tools that require it. [1] [2]
• Added aiohttp as an override dependency in the backend Python project for compatibility.

Template and Build System Updates:

• Updated Bicep-generated template metadata to reflect the use of a newer Bicep compiler version. [1] [2] [3]
• Minor changes to resource dependency ordering in ARM templates for consistency. [1] [2]

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