Patch policy library for Azure China

[faister]

Overview/Summary

This PR ensures policy definitions/policy set definitions along with policy assignments all work in Azure China. Internal SE backlog item here. This is because there are some policy definition differences in China especially wrt to the MS Defender for Cloud policies, hence there was a separate policy assignment definition in the upstream enterprise-scale repo.

Just to be sure, re-tested the entire deployment flow as per https://github.com/Azure/ALZ-Bicep/wiki/DeploymentFlow and made some fixes.

This PR fixes/adds/changes/removes

1. Tested default policy assignments by introducing a new infra-as-code\bicep\modules\policy\assignments\alzDefaults\mc-alzDefaultPolicyAssignments.bicep file.
2. Added separate lib/china folder under infra-as-code\bicep\modules\policy\assignments\lib\china\policy_assignments. Also added default policy assignments which would work in Azure China.
3. Updated and tested Mooncake workflow file, and script to create separate lib/china folder under policy/assignments.
4. Added customer usage attribution module in customRoleDefinitions module.
5. Also fixes the deployment errors during MC testing found by @jfaurskov in Module Bicep template and parameter file hygiene #227

Breaking Changes

1. None

Testing Evidence

Tested workflow manual run successfully in my forked repo

As part of this Pull Request I have

• Read the Contribution Guide and ensured this PR is compliant with the guide
• Checked for duplicate Pull Requests
• Associated it with relevant GitHub Issues
• (ALZ Bicep Core Team Only) Associated it with relevant ADO Items
• Ensured my code/branch is up-to-date with the latest changes in the main branch
• Performed testing and provided evidence.
• Updated tests (if required) Unit - Linting - E2E (End-To-End)
• Updated relevant and associated documentation (e.g. Contribution Guide, Module READMEs, Wiki Docs etc.)
• If relevant, created or updated Code Tours here

[jfaurskov]

Nice work @faister :-) Added a couple of suggestions. Also If you could merge with main and put the validation of the mc-alzdefaultpolicyassignments into the /tests/pipelines/mc-base-unit-validate.yml pipeline in place of the current alzdefaultpolicyassignments (line 81 - 87) that would be ace!

[faister]

Nice work @faister :-) Added a couple of suggestions. Also If you could merge with main and put the validation of the mc-alzdefaultpolicyassignments into the /tests/pipelines/mc-base-unit-validate.yml pipeline in place of the current alzdefaultpolicyassignments (line 81 - 87) that would be ace!

Thanks @jfaurskov, done updated tests/pipelines/mc-base-unit-validate.yml and tested it in az cli successfully. see attached output.
Az CLI Validate Alz Default policy assignments-succeeded.txt

[jfaurskov]

/azp run ValidateAzCloud

[jfaurskov]

/azp run ValidateMcCloud

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[jfaurskov]

/azp run ValidateAzCloud

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[jfaurskov]

/azp run ValidateAzCloud

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).