Obsolete dynamic to static private IP conversions

I think this is being used in multiple arm templates for example here:
[vm-automatic-static-ip](https://github.com/Azure/azure-quickstart-templates/tree/master/quickstarts/microsoft.compute/vm-automatic-static-ip)

### Issue Details
There seems to be a common misconception what dynamic in the context of azure private IPs actually means. I am guessing this is because the behaviour changed in ~2018
https://github.com/MicrosoftDocs/azure-docs/commit/f71352ed4682049ba223b6e80f2e43307b884008

This means all the dynamic -> static incremental deployments for this purpose no longer do anything useful. You would have the same behavior if you leave the NIC on dynamic. I suggest to remove this everywhere to make clear that this is no longer needed.

References #12078

Docs:
https://github.com/MicrosoftDocs/azure-docs/blob/4bc20bec0b678d282233f6a67eed633034ad24fa/articles/virtual-network/ip-services/private-ip-addresses.md?plain=1#L38-L54
https://github.com/MicrosoftDocs/azure-docs/blob/798be06dee9d57c838412a459d03e5f0b2afaf10/articles/virtual-network/virtual-network-network-interface.md?plain=1#L49

Start with the vm-automatic-static-ip quickstart and search the repository for ARM templates that convert dynamic private IP allocation to static. Read the linked Azure documentation to confirm the current behavior, then remove the obsolete conversions from each affected template. Done means the unnecessary dynamic-to-static steps are no longer present in the identified templates.

Written by the indexing model from the issue text.