feat: Merge the AVM WAF and Azd Quota check changes from dev to main

[Abdul-Microsoft]

Purpose

This pull request introduces significant changes to the deployment process, infrastructure configuration, and documentation for the Azure-based solution. The updates focus on aligning the architecture with Azure's Well-Architected Framework (WAF), simplifying infrastructure definitions, and enhancing deployment options for both sandbox and production environments. Below is a summary of the most important changes:

Deployment and Infrastructure Updates:

• Updated .github/workflows/deploy.yml to rename the AzureAiServiceLocation parameter to aiDeploymentsLocation for consistency in deployment scripts.
• Removed legacy Bicep files (infra/deploy_ai_foundry.bicep, infra/deploy_keyvault.bicep, infra/deploy_managed_identity.bicep) to streamline infrastructure definitions. These functionalities are now consolidated into the main deployment process. [1] [2] [3]
• Added new parameters to infra/main.parameters.json for enhanced configurability, including solutionName, deploymentType, llmModel, and gptModelVersion.

Documentation Enhancements:

• Expanded the README.md to describe the new WAF-aligned architecture option, linking to detailed documentation and deployment guides.
• Introduced a new file, docs/ArchitectureWAF.md, detailing the WAF-aligned architecture, its pillars (e.g., security, cost optimization), and deployment configuration.
• Updated docs/DeploymentGuide.md to include instructions for choosing between sandbox and WAF-aligned deployment options, with guidance on parameter adjustments for production environments. [1] [2]

Configuration Simplifications:

• Removed the environment and preprovision hooks in azure.yaml, simplifying the deployment configuration by eliminating unused or redundant steps. [1] [2]
• Consolidated infrastructure parameters in infra/main.bicepparam and removed hardcoded values, improving flexibility for different deployment scenarios.

These changes collectively enhance the scalability, security, and maintainability of the solution while providing clearer guidance for users deploying the architecture in various environments.

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

[github-actions]

🎉 This PR is included in version 1.4.2 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀