feat: dev downmerge, updated for existing AI Foundry in Bicep & scripts

[Ragini-Microsoft]

Purpose

This pull request introduces several updates across workflow configurations, documentation, and infrastructure deployment scripts. The changes primarily focus on improving deployment flexibility, enhancing documentation, and aligning configurations with updated dependencies. Below is a categorized summary of the most significant changes:

Workflow Configuration Updates

• Adjusted minimum capacities for GPT and text embedding models in .github/workflows/deploy.yml to optimize resource allocation (GPT_MIN_CAPACITY reduced to 150, TEXT_EMBEDDING_MIN_CAPACITY increased to 80).
• Added support for specifying aiDeploymentsLocation and capturing AI_SEARCH_SERVICE_NAME in deployment workflows. [1] [2]
• Introduced a new workflow .github/workflows/telemetry-template-check.yml to validate the presence of a required telemetry template line in azure.yaml.

Documentation Enhancements

• Updated docs/DeploymentGuide.md to reflect new Azure Developer CLI version requirements (v1.15.0+) and additional parameters for sample data processing scripts. [1] [2]
• Revised docs/QuotaCheck.md to align default model capacities and supported regions with updated configurations. [1] [2]
• Removed outdated or redundant environment variable descriptions from docs/README_LOCAL.md. [1] [2]

Infrastructure Deployment Improvements

• Enhanced infra/deploy_ai_foundry.bicep with support for existing AI Foundry resources and added system-assigned identities for aiSearch resources. [1] [2]
• Refactored output variables in infra/deploy_ai_foundry.bicep to include aiSearchConnectionName and aiFoundryRgName. [1] [2]
• Simplified parameters in infra/deploy_app_service.bicep by removing unused fields like AzureSearchKey and useAiFoundrySdk. [1] [2]

Code Quality and Linting

• Updated .github/workflows/pylint.yml to exclude test files from linting with flake8.

These changes collectively improve the maintainability, clarity, and efficiency of the deployment pipeline and associated documentation.

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

• I have built and tested the code locally and in a deployed app
• For frontend changes, I have pulled the latest code from main, built the frontend, and committed all static files.
• This is a change for all users of this app. No code or asset is specific to my use case or my organization.

Other Information

[github-actions]

🎉 This PR is included in version 1.6.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀