Update newWorkload example to resolve naming related conflicts

[ExchMaster]

Description

Updated the newWorkload example in the following ways

• Applied the shared variable file pattern Apply the shared variable file pattern to the newWorkload example #569
• Modified the storageAccountName by including subscriptionId as a param of uniquestring function The new workload example creates a non-unique storage account name  #523
• Modified the spokeNetwork peering name to not exceed 64 (take function) and significantly reduced the risk of using 64 characters by removing extra params from spokeNetwork peering name. BICEP: Autogenerated deployment name in NewWorkload template exceeds max length #393

Issue reference

The issue this PR will close the following related issues:

• Apply the shared variable file pattern to the newWorkload example #569
• The new workload example creates a non-unique storage account name  #523
• BICEP: Autogenerated deployment name in NewWorkload template exceeds max length #393

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

[glennmusa]

Peered up successfully, created a unique storage account, and truncates the deployment name.

Have a comment in here about naming conventions, but we can plan to solve that for all the add-ons at once instead of piecemeal-ing it one-by-one.