Template CLEANUP LOG

It's been a great year with the repo receiving an amazing number of templates across an even more amazing breadth of Azure services. As we've progressed there are some templates that have become repetitive and don't serve a good purpose anymore. This logs the templates we're removing/merging or moving to different paths.

---

REMOVED
- 101-create-backup-vault-policy → Fails consistently
- 101-simple-windows-vm-data-disk → Merged with 101-simple-windows-vm
- 101-vm-simple-linux-vm-data-disk → Merged with 101-vm-simple-linux-vm
- 101-virtual-network → Merged into 101-vnet-two-subnets
- 101-create-availability-set → Merged into 101-create-availability-set-3FDs-20UDs
- 101-create-storage-account-premium, → Merged into 101-storage-account-create

  101-create-storage-account-standard
- 101-networkinterface-with-publicip-vnet, → Merged into 101-nic-publicip-dns-vnet

  101-public-ip-dns-name
- 201-2-vms-2-FDs-no-resource-loops → Removed since a lot of templates deliver the same functionality
- chef-extension-windows-vm → Chef extension template with JSON parameters is now available
- hortonworks-on-centos → Broken template, doesn't work
- resource-loop-vms-userimage → All complex templates are now using copyIndex (resource loops). 301-custom-images-at-scale is a better template for this.
- resource-loop-vms-vnet-aset → All complex templates are now using copyIndex (resource loops). This isn't needed anymore.
- resource-loop-vms-vnet → All complex templates are now using copyIndex (resource loops). This isn't needed anymore.
- mesos-swarm-marathon → Replaced with 101-acs-mesos & 101-acs-swarm

RENAMED
- 101-create-application-gateway → 101-application-gateway-create
- 101-create-availability-set-3FDs-20UDs → 101-availability-set-create-3FDs-20UDs
- 101-create-backup-vault → 101-backup-vault-create
- 101-create-documentdb-account-consistencypolicy → 101-documentdb-account-consistencypolicy-create
- 101-create-documentdb-account → 101-documentdb-account-create
- 101-create-expressroute-circuit → 101-expressroute-circuit-create
- 101-create-internal-loadbalancer → 101-internal-loadbalancer-create
- 101-create-key-vault → 101-key-vault-create
- 101-create-security-group → 101-security-group-create
- 101-create-site-to-site-vpn → 101-site-to-site-vpn-create
- 101-linux-vm-serial-output → 101-vm-linux-serial-output
- 101-simple-linux-vm → 101-vm-simple-linux
- 101-simple-windows-vm → 101-vm-simple-windows
- 101-tags-vm → 101-vm-tags
- resource-loop-vms-vnet → 201-vm-copy-index-loops
- windows-vm-custom-script → 201-vm-custom-script-windows
- 201-windows-vm-diagnostics-extension → 201-vm-diagnostics-extension-windows
- windows-vm-push-certificate → 201-vm-push-certificate-windows
- 201-scale-existing-vmss → 201-vmss-scale-existing
- web-app-dsc-vm → 201-web-app-vm-dsc
- vm-d14-high-iops-32-data-disks → 301-vm-32-data-disks-high-iops
- windows-puppet-agent → puppet-agent-windows
- extend-vnet-to-multi-vnet → 201-extend-vnet-to-multi-vnet
- node-mongodb-high-availability → mongodb-nodejs-high-availability
- ubuntu-desktop → ubuntu-desktop-gnome
## \*

The issue names the template paths affected by the REMOVED and RENAMED lists, but no source files or tests. Start by checking those paths in the repository and comparing them with the stated replacements. The issue does not define a new change or a completion test, so the intended done state is unclear.

Written by the indexing model from the issue text.