The new workload example creates a non-unique storage account name

[jjansen23]

Description

The new workload example creates a non-unique storage account name when the workload is the same name as the root MLZ deployment name

Steps to Reproduce

Steps to reproduce the behavior:

1. Run the following with the appropriate information inserted.
   az deployment sub create
   --subscription f2e773f1-885e-4b87-9cda-89db1723cc61
   --location eastus
   --name tier3
   --template-file "./newWorkload.bicep"
   --parameters
   workloadName="tier3"
   hubSubscriptionId=""
   hubResourceGroupName=""
   hubVirtualNetworkName=""
   hubVirtualNetworkResourceId=""
   logAnalyticsWorkspaceResourceId=""
   firewallPrivateIPAddress=""

Expected behavior

A new tier 3 vnet is created

Actual behavior

{"error":{"code":"InvalidTemplateDeployment","message":"The template deployment 'tier3' is not valid according to the validation procedure. The tracking id is '53ad4a79-11cf-46f0-b450-9869f228a2e7'. See inner errors for details.","details":[{"code":"PreflightValidationCheckFailed","message":"Preflight validation failed. Please refer to the details for the specific errors.","details":[{"code":"StorageAccountAlreadyTaken","target":"Storage-account-name","message":"The storage account named Storage-account-name is already taken."}]}]}}

Screenshots

Additional context

Operating System:
Terraform Version:
Cloud (public, Azure Government, etc.):