chore: Add tags to prevent SFI W18 Policy violation

[NirajC-Microsoft]

Purpose

This pull request focuses on improving tag management and making minor template and dependency adjustments in the infrastructure codebase. The most significant change is the merging of resource group tags with custom tags to ensure that all relevant metadata is applied to resources. Additionally, there are updates to the handling of dependencies, template generator metadata, and ARM template expressions for improved clarity and maintainability.

Tag management improvements:

• Updated the tags property in both infra/main.bicep and infra/main_custom.bicep to merge resourceGroup().tags with allTags, ensuring resources inherit both resource group and custom tags. [1] [2]
• Changed the ARM template (infra/main.json) to use shallowMerge for combining resource group tags and custom tags, aligning with the Bicep changes.

Template and dependency adjustments:

• Reordered some dependsOn arrays in infra/main.json to improve deployment sequencing and clarity. [1] [2]
• Updated ARM template expressions for the scope property to use format instead of resourceId, improving readability and consistency. [1] [2] [3] [4] [5] [6]

Template generator metadata:

• Updated the Bicep generator version and template hash in multiple places in infra/main.json to reflect the version used for this deployment. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12]

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