Generate uniqueData for Private Link resources in an idempotent manner

[BrandonSharp]

Description

The current method for generating uniqueData for use in naming resources prevents idempotent deployment because an attempt to create a new AMPLS resource results in a conflict with the previous one. This additionally leads to multiple private endpoints getting created, which could eventually exhaust IP space in the subnet over time if deployed enough times.

I propose that if this is generated using the uniqueString Bicep function instead, the random string will be generated in a repeatable manner, provided future deployments are both to the same subscription, and with the same deployment name. Manual testing in an Azure Gov subscription seems good as far as I can tell.

Relevant change is to L22. The remainder are corrections to whitespace by the Bicep plugin in VS Code.

Issue reference

The issue this PR will close: #700

Checklist

Please make sure you've completed the relevant tasks for this PR out of the following list:

• All acceptance criteria in the backlog item are met
• The documentation is updated to cover any new or changed features
• Manual tests have passed
• Relevant issues are linked to this PR

[ghost]

All CLA requirements met.

[lisamurphy-msft]

/azp run

[azure-pipelines]

Azure Pipelines could not run because the pipeline triggers exclude this branch/path.

[lisamurphy-msft]

Greetings @BrandonSharp Thank you for your PR. Will review and test momentarily.