fix: Add Dynamic Environment Name Generation Logic and Input Parameter Handling

[Prasanjeet-Microsoft]

Purpose

• This PR introduces changes to the CI pipeline (CI.yml) to generate a unique ENVIRONMENT_NAME at runtime, ensuring that:

  • Parallel or repeatable deployments don't conflict.
  • Resource Group names are unique and traceable.
  • Cleanup logic can target specific deployments based on generated names.

Does this introduce a breaking change?

• Yes
• No

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:

• CI pipeline successfully generates and outputs a unique ENVIRONMENT_NAME.
• The generated environment name is passed correctly to the PowerShell script.
• Resource groups are created and referenced using the new environment name.
• Resource cleanup logic works as expected, even on failure.
• No breaking changes were introduced in the workflow.

[github-actions]

🎉 This PR is included in version 1.0.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀