Enable new Windows volume resize test after upstream fix for missing `ClientNodeSelection`

[torredil]

/kind cleanup

What happened?

New Kubernetes resize e2e test ([It] External Storage [Driver: ebs.csi.aws.com] [Testpattern: Dynamic PV (ntfs)(allowExpansion)] [Feature:Windows] volume-expand should resize volume when PVC is edited and the pod is re-created on the same node after controller resize is finished) is failing with the following error:

I1016 18:19:18.607888 26711 dump.go:53] At 2025-10-16 18:14:47 +0000 UTC - event for pod-efb085b2-2a2c-44d3-b6fa-c62d41c0784c: {kubelet ip-192-168-70-254.us-west-2.compute.internal} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to setup network for sandbox "345c59e27569f0507017e03f941b4b1fd719d66b1fce2b92458a12a603c96443": plugin type="vpc-bridge" name="vpc" failed (add): failed to parse Kubernetes args: failed to get pod IP address pod-efb085b2-2a2c-44d3-b6fa-c62d41c0784c: error executing k8s connector: error executing connector binary: exit status 1 with execution error: pod pod-efb085b2-2a2c-44d3-b6fa-c62d41c0784c does not have label vpc.amazonaws.com/PrivateIPv4Address

Example logs: https://prow.k8s.io/view/gs/kubernetes-ci-logs/pr-logs/pull/kubernetes-sigs_aws-ebs-csi-driver/2666/pull-aws-ebs-csi-driver-test-e2e-external-eks-windows/1978880503536685056

What you expected to happen?

The test should pass successfully.

How to reproduce it (as minimally and precisely as possible)?

1. Run the Kubernetes 1.34 e2e test suite against an EKS Windows cluster with latest driver.
2. Execute the test: External Storage [Driver: ebs.csi.aws.com] [Testpattern: Dynamic PV (ntfs)(allowExpansion)] [Feature:Windows] volume-expand should resize volume when PVC is edited and the pod is re-created on the same node after controller resize is finished
3. Observe the failure when the second pod is created.

Anything else we need to know?:

This is a bug in the upstream test code. The issue occurs because the second pod created in the test does not include the ClientNodeSelection configuration.

This issue tracks the upstream fix and re-enabling the test once it is fixed.