Modify naming logic

[brooke-hamilton]

Benefit/Result/Outcome

To create predictable, consistent names that conform with naming guidelines.

Description

The scope of this work includes:

• Standardized letter casing
• User-defined naming prefix (existing) and a new user-defined suffix.
• Requiring the naming prefix (previously it was optional)
• No longer using the AZ CLI deployment name in the Bicep template.
• Generating random name fragments where necessary

Please consider breaking this work into multiple PRs. I created this as a single backlog item so that the person doing the work can decide how to organize the engineering, but the scope of these changes is large and potentially disruptive to other work. A set of individual PRs can minimize the impact of the overall large changes.

The discussion that led to this backlog item is #531

Acceptance Criteria

• All resource names are in lower case
• An additional optional parameter is defined as resourcePostfix which allows deploying into the same subscriptions but different regions. It will default to "mlz".
• Include resourcePostfix in automatic tags.
• The seed for unique() calculations is the concatenation of resourcePrefix and resourcePostfix.
• Naming guidelines for resource abbreviations are implemented
• A naming convention is implemented.

[brooke-hamilton]

This backlog item is superseded by #556.