FirewallPolicyRuleApplicationProtocol port number should go up to 65535, according to Azure blog post

Hey there! I'm an engineer at LinkedIn working on building some automation for managing Azure firewall rules. I'm working off the spec [here](https://docs.microsoft.com/en-us/azure/templates/microsoft.network/firewallpolicies/rulecollectiongroups?tabs=bicep#firewallpolicyruleapplicationprotocol) which says:
`Port number for the protocol, cannot be greater than 64000.`

However, I see in a [blog post from 2020](https://azure.microsoft.com/en-us/blog/new-azure-firewall-certification-and-features-in-q1-cy2020/) that allegedly using a port number of up to 65535 should now be available (see the section `High ports restriction relaxation now generally available`).

That seems to contradict the specification and documentation [here](https://github.com/Azure/azure-rest-api-specs/blob/b69b3fa5c26c94aa6efe6dadb76f599c204f297b/specification/network/resource-manager/Microsoft.Network/stable/2021-03-01/firewallPolicy.json#L1034).

Which of these two should be treated as the source of truth? I feel like to avoid confusion (as this was confusing for my team), we should probably either change the restspecs to match the blog post, or redact the blog post.

Start with specification/network/resource-manager/Microsoft.Network/stable/2021-03-01/firewallPolicy.json at the referenced line, then compare its port limit with the linked Azure template documentation and the blog post's high-ports section. Confirm which limit is authoritative and update the REST specification or related documentation so the sources no longer conflict.

Written by the indexing model from the issue text.