adding ARM modules

[krnese]

This PR fixes

• Re-structuring the ARM templates for all resource deployments
• eslzArm.json is used to orchestrate the e2e composition of ESLZ, and subsequent resource deployments based on user input from portal experience
• The composite ARM templates can be sequenced on their own, independently of each other (although strict sequencing is required to ensure the same outcome)
• Customers can deploy from private repository if they want to sequence at their own pace
• Converging Contoso, AdventureWorks, and Wingtip into one ESLZ deployment experience via first-party deployment in Azure portal
• Removing individual policy assignment for Azure Monitor for VMs, and are now using the built-in policy initiative to achieve the same which spans Windows, Linux (VM and VMSS), as well as Azure Arc enabled VMs.
• Deploy Log Analytics DINE policy has moved to built-in, hence removing the custom policy from ESLZ and use built-in for assignment at the management management group
• Support N network topologies in same experience (hub and spoke, vwan, hub and spoke with NVA)
• Optimizing the execution graph
• Added option for peering virtual network in identity subscription (nva, hub and spoke, and vwan)
• Added option for peering landing zones to connectivity subscription when hub & spoke is the selected topology (VWAN is excluded due to concurrency issues)
• Navigate policy assignment for identity, when using single vs dedicated subscriptions for platform purposes
• Moving several of the diagnostics policies to built-in, and updating the diagnostics initiative (this means there's a new resource name as update of existing one will not be allowed due to removal of parameters)
• Adding policy initiative for denying public endpoints (using built-ins)
• Adding policy initiative for enforcing private dns zone association with private link (using built-ins)
• Updated description and display name for all policy assignments

[daltondhcp]

Fantastic improvements! Looks good to me.