refactor: added post-deployment guide and updated post deployment scripts for users deployed using AVM template

[Harsh-Microsoft]

Purpose

This pull request introduces significant improvements to the deployment process and documentation for the Document Knowledge Mining Solution Accelerator. The main changes include enhanced support for AVM (Azure Verified Modules) deployments, improved post-deployment guidance, and increased flexibility in the deployment scripts and infrastructure templates. The most important changes are grouped as follows:

Deployment Script Enhancements

• Added a ResourceGroupName parameter to resourcedeployment.ps1, allowing the script to support both AVM (custom ARM/Bicep) and azd up deployment flows. The script now conditionally loads environment values or deployment outputs based on this parameter. [1] [2] [3] [4] [5]
• Improved mapping of deployment outputs in the PowerShell script by adding a new method MapResultAz to populate environment variables from resource group deployment outputs, supporting AVM scenarios.

Documentation Updates

• Added a comprehensive AVMPostDeploymentGuide.md documenting post-deployment steps specifically for AVM deployments, including prerequisites, script usage, TPM configuration, and next steps.
• Updated DeploymentGuide.md with clear instructions for both azd up and AVM deployment flows, including which script parameters to use for each scenario.

Infrastructure Template Improvements

• Updated infra/main.bicep and infra/main.json to tag resource groups with the deployment name and created-by user, improving traceability and supporting script automation. [1] [2] [3]
• Corrected resource dependency order and improved monitoring configuration logic to support existing Log Analytics workspaces. [1] [2]

Parameter and Default Value Adjustments

• Changed the default GPT model capacity from 150 to 100 in the infrastructure template to better align with recommended quotas.

These changes collectively make the deployment process more robust, flexible, and easier to follow for both AVM and azd users.

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.1.1 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀