[sig-windows] kube-proxy crash loop: hcnCreateLoadBalancer failed in Win32: The specified port already exists (0x803b0013)

What's the problem?

### What happened? The issue only occurred after upgrading Windows Server OS 2019 from Build `17763.8027` to Build `17763.8146`. The Windows nodes depends on Windows networking stack, corresponding `kube-proxy` without CNI. On Windows nodes, when a LoadBalancer or NodePort service has its backing endpoints scaled to 0, `kube-proxy` fails to release the underlying Host Networking Service (HNS) port lock. When endpoints are scaled back up, `kube-proxy` attempts to recreate the policy, hits a collision with the orphaned lock, and enters a crash loop, throwing the following Windows HNS error: ``` proxier.go:1604] "Nodeport policy creation failed" err="hcnCreateLoadBalancer failed in Win32: The specified port already exists. (0x803b0013) {\"Success\":false,\"Error\":\"The sp ecified port already exists. \",\"ErrorCode\":2151350291}" nodeport=30364 sourceVip="" proxierIPFamily="IPv4" nodeIP="10.0.0.4" ``` This is exposed by a recent OS-level change. On older Windows Server builds (e.g., `1...