fix: add dependency to private endpoints for container apps

[Harsh-Microsoft]

Purpose

This pull request updates deployment dependencies in the infrastructure code to ensure that private endpoints are provisioned before dependent container app resources. The changes affect both the Bicep (infra/main.bicep) and the generated ARM template (infra/main.json), improving deployment reliability and sequencing.

Dependency management improvements:

• Added cognitiveServicePrivateEndpoint and contentUnderstandingPrivateEndpoint as dependencies for the avmContainerApp_update module to ensure these endpoints are created before the container app is deployed (infra/main.bicep).
• Added cognitiveServicePrivateEndpoint as a dependency for the avmContainerApp_API_update module (infra/main.bicep).
• Updated the corresponding dependsOn arrays in the generated ARM template to reflect these new dependencies for both avmContainerApp_update and avmContainerApp_API_update resources (infra/main.json). [1] [2]

Resource dependency ordering adjustments:

• Reordered entries in the dependsOn arrays for private DNS zones to ensure correct sequencing of DNS zone provisioning (infra/main.json). [1] [2]

Other:

• Updated the templateHash in infra/main.json due to the changes in the Bicep template (infra/main.json).

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

The release is available on GitHub release

Your semantic-release bot 📦🚀