capture definitionReferenceId that starts with number.

[eureka-gh]

Overview/Summary

We (slz engineering team) found an issue in alz's invoke-policyToBicep.ps1. This script doesn't support any definitionReferenceId that starts with number. E.g. We have a policySet definitions that pulled from azure built-in policy, the definitionReferenceId is like '10006169408036501401'. The invoke-policyToBicep.ps1 generates _policySetDefintionsBicepInput.txt like this.

It uses .10006169408036501401 to reference an object which is illegals for neither json nor bicep. The invoke-policyToBicep.ps1 somehow missed to handle this case.

This PR fixes/adds/changes/removes

1. adding a regex to capture defintionReferenceId that starts with number.
   $definitionReferenceIdForParameters -match '^[0-9].+'

Breaking Changes

N/A

Testing Evidence

with this pr, we can see the result diff in the output of the invoke-PolicyToBicep.ps1

As part of this Pull Request I have

• Read the Contribution Guide and ensured this PR is compliant with the guide
• Ensured the resource API versions in .bicep file/s I am adding/editing are using the latest API version possible
• 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 one or more of the following tests (if required)
  • Unit
  • Linting
  • E2E (End-To-End)
  • ValidateAzCloud (Base validation in Azure Cloud)
  • ValidateMcCloud (Base validation in Azure China Cloud)
• Updated relevant and associated documentation (e.g. Contribution Guide, Module READMEs, Wiki Docs etc.)
• If relevant, created or updated Code Tours here

[jtracey93]

/azp run validateazcloud

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[jtracey93]

LGTM 👍