fix: Code change to load newly created task on left side panel (fix for bug 23829).

[NirajC-Microsoft]

Purpose

This pull request introduces several improvements and fixes across deployment workflows, infrastructure scripts, and documentation. The main themes are enhanced post-deployment automation and user guidance, improved parameter handling for scripts, and more robust deployment workflow configuration.

Post-deployment automation and documentation:

• Added a comprehensive AVMPostDeploymentGuide.md documenting post-deployment steps, prerequisites, and usage instructions for AVM-based deployments, improving clarity for users setting up the solution after infrastructure provisioning.

Infrastructure and script enhancements:

• Refactored Team-Config-And-Data.ps1 to support both azd and direct Azure deployments, with interactive subscription selection, improved error handling, and dynamic retrieval of configuration values; now passes AzSubscriptionId to sub-scripts for consistency. [1] [2]
• Updated Process-Sample-Data.ps1 and Upload-Team-Config.ps1 to accept and use the new AzSubscriptionId parameter, ensuring correct Azure context and resource access during post-deployment configuration. [1] [2] [3] [4]

Deployment workflow and quota handling:

• Reduced GPT_MIN_CAPACITY default and usage from 150 to 1 in .github/workflows/deploy.yml to lower resource requirements for deployments. [1] [2] [3]
• Removed the e2e-test job from the deployment workflow and updated dependencies for cleanup-deployment, simplifying the pipeline.
• Improved quota check logic in infra/scripts/checkquota.sh to set INSUFFICIENT_QUOTA when model quota information is missing, making quota validation more robust.

Resource tagging for traceability:

• Added DeploymentName to resource group tags in both infra/main.bicep and infra/main_custom.bicep, improving traceability of deployments. [1] [2]

Testing workflow improvements:

• Expanded test coverage exclusion in test.yml by ignoring additional test files, allowing more targeted and efficient test runs.
• ...

Does this introduce a breaking change?

• Yes
• No

How to Test

• Get the code

git clone [repo-address]
cd [repo-name]
git checkout [branch-name]
npm install

• Test the code

What to Check

Verify that the following are valid

• ...

Other Information