feat: avm module upgrade for macae

[AjitPadhi-Microsoft]

Description

This pull request introduces three new Bicep modules to support AI project, AI services deployment, and AI Foundry connections, and removes the custom implementation for Container App Environment in favor of a standardized AVM module. The changes enhance modularity, reusability, and support for advanced configuration of Azure AI and container resources.

New modules for AI resource management:

• Added ai-project.bicep module to create and manage AI Foundry projects within an existing Cognitive Services account, with support for custom descriptions, tags, and outputs for key identifiers and endpoints.
• Added ai-services-deployments.bicep module to manage deployments and role assignments for Cognitive Services accounts, supporting a wide range of built-in roles, deployment SKUs, and flexible configuration through parameterized inputs.
• Added aifp-connections.bicep module to create AI Foundry project connections to Azure Cognitive Search, including secure API key handling and metadata configuration.

Container App Environment module simplification:

• Removed the custom implementation of container-app-environment.bicep, which handled environment creation, monitoring, redundancy, and networking logic, in favor of using the AVM public module for managed environments. This reduces code duplication and leverages standardized best practices.

Pipeline Reference

Pipeline

Type of Change

• Azure Verified Module updates:
  • Bugfix containing backwards-compatible bug fixes, and I have NOT bumped the MAJOR or MINOR version in version.json:
  • Feature update backwards compatible feature updates, and I have bumped the MINOR version in version.json.
  • Breaking changes and I have bumped the MAJOR version in version.json.
  • Update to documentation
• Update to CI Environment or utilities (Non-module affecting changes)

Checklist

• I'm sure there are no other open Pull Requests for the same update/change
• I have run Set-AVMModule locally to generate the supporting module files.
• My corresponding pipelines / checks run clean and green without any errors or warnings
• I have updated the module's CHANGELOG.md file with an entry for the next version

[microsoft-github-policy-service]

Important

The "Needs: Triage 🔍" label must be removed once the triage process is complete!

Tip

For additional guidance on how to triage this issue/PR, see the BRM Issue Triage documentation.

[microsoft-github-policy-service]

Important

If this is a module-related PR, being submitted by the sole owner of the module, the AVM core team must review and approve it (as module owners can't approve their own PRs).

To indicate this PR needs the core team''s attention, apply the "Needs: Core Team 🧞" label!

The core team will only review and approve PRs that have this label applied!