fix: CI Pipeline Validate Deployment - DKM

[VishalS-Microsoft]

Purpose

This pull request introduces improvements to resource tagging and metadata in both the deployment pipeline and infrastructure templates. The main goal is to enhance traceability and provide better context for deployed resources, especially around creation date and networking configuration.

Deployment pipeline enhancements:

• Added a step to generate a UTC timestamp in the format YYYY-MM-DDTHH:MM:SS.SSSSSSSZ and store it in the current_date variable for use in resource tagging.
• Updated the Azure deployment command to include a tags parameter, adding SecurityControl, Purpose, and CreatedDate tags to resources created during validation. The CreatedDate tag uses the generated timestamp.

Infrastructure template improvements:

• Modified the TemplateName tag in the resourceGroupTags resource in infra/main.bicep to dynamically reflect whether private networking is enabled. It now sets the value to DKM-WAF when private networking is enabled, otherwise DKM.

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

The release is available on GitHub release

Your semantic-release bot 📦🚀