Fix: Updated Deny-MgmtPorts-From-Internet.json to recognize 0.0.0.0/0 as being equivalent to * to represent all remote IP addresses

Overview/Summary

Replace this with a brief description of what this Pull Request fixes, changes, etc.

This PR fixes/adds/changes/removes

The policy checks for the source address to be * or Internet, but doesn't check for 0.0.0.0/0. Per https://learn.microsoft.com/en-us/azure/virtual-network/network-security-groups-overview "0.0.0.0/0 in the Source and Destination columns represents all addresses"

Breaking Changes

Any deployed NSG's which were previously bypassing this policy by using 0.0.0.0/0 will be denied as non-compliant.

Testing Evidence

Testing URLs

The below URLs can be updated where the placeholders are, look for {YOUR GITHUB BRANCH NAME HERE - Remove Curly Brackets Also} & {YOUR GITHUB BRANCH NAME HERE - Remove Curly Brackets Also}, to allow you to test your portal deployment experience.

Please also replace the curly brackets on the placeholders {}

Azure Public

Azure US Gov (Fairfax)

As part of this Pull Request I have

[X] Checked for duplicate Pull Requests
[X] Associated it with relevant issues, for tracking and closure.
[X] Ensured my code/branch is up-to-date with the latest changes in the main branch
[X] Performed testing and provided evidence.
[X] Ensured contribution guidance is followed.
[NA] Updated relevant and associated documentation.
[X] Updated the "What's New?" wiki page (located: /docs/wiki/whats-new.md)

Azure / Enterprise-Scale

Fix: Updated Deny-MgmtPorts-From-Internet.json to recognize 0.0.0.0/0 as being equivalent to * to represent all remote IP addresses #1768