chore: Dev to main

[NirajC-Microsoft]

Purpose

This pull request refactors how the Azure Search Service resource is provisioned and referenced in the infrastructure code, primarily by switching from a module-based deployment to a direct resource declaration, and updating all related outputs and configuration references. It also updates the Azure API versions for multiple resource deployments to ensure compatibility with newer features and improves deployment reliability and performance.

Azure Search Service resource provisioning and references:

• Replaces the avmSearchSearchServices module with a direct Microsoft.Search/searchServices resource declaration (avmSearchSearchServices), and introduces a separate update module (avmSearchSearchServicesUpdate) to handle managed identity and additional properties, reducing deployment time (infra/main.bicep, infra/main.json). [1] [2] [3]
• Updates all references to the Azure Search Service name and endpoint in outputs and configuration to use the new resource's name property and the aiSearchName variable, instead of module outputs (infra/main.bicep, infra/main.json). [1] [2] [3] [4] [5] [6] [7] [8]

API version updates for resource deployments:

• Updates the apiVersion for all Microsoft.Resources/deployments resources from 2022-09-01 to 2025-04-01 for improved compatibility and access to new features (infra/main.json). [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13] [14] [15] [16] [17] [18]

Metadata and template updates:

• Updates Bicep generator metadata and template hashes to reflect the new Bicep version (0.40.2.10011) for both main and nested templates (infra/main.json). [1] [2] [3]

Deployment dependency management:

• Adds explicit dependency on the new Azure Search Service resource for related modules to ensure correct deployment order (infra/main.bicep, infra/main.json). [1] [2]

Configuration values for App Configuration:

• Updates configuration values for Azure Search Service and Cosmos DB connection strings in App Configuration to use the new resource references and API versions (infra/main.bicep, infra/main.json). [1] [2] [3] [4]

Let me know if you have any questions about these changes or need clarification on how to reference the new Azure Search Service resource in your code!

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