dnsConfig are ignored for Windows pods

I'm running EKS K8S 1.30 with EC2 Windows workers nodes only, coredns runing on fargate
There is an issue with `dnsConfig` that are ignored for Windows pods:

```
spec:
dnsPolicy: "None"
dnsConfig:
nameservers:
- 192.168.1.100
searches:
- custom.domain
```
C:\app>ipconfig /all
```
Windows IP Configuration

Host Name . . . . . . . . . . . . : eks-app
Primary Dns Suffix . . . . . . . : custom.domain
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : custom.namespace.svc.cluster.local
svc.cluster.local
cluster.local

Ethernet adapter vEthernet (cid-54890e7f-6a27-434b-ab4c-12ba9c74c1e6):

Connection-specific DNS Suffix . : custom.namespace.svc.cluster.locall
Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Container Adapter
Physical Address. . . . . . . . . : 00-15-5D-21-52-E4
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::e67b:4cd8:d426:be86%18(Preferred)
IPv4 Address. . . . . . . . . . . : 10.50.130.207(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.50.130.1
DNS Servers . . . . . . . . . . . : 172.20.0.10
NetBIOS over Tcpip. . . . . . . . : Disabled
Connection-specific DNS Suffix Search List :
custom.namespace.svc.cluster.local
svc.cluster.local
cluster.local
```

**Expected to happen:**
```
Windows IP Configuration

Host Name . . . . . . . . . . . . : eks-app
Primary Dns Suffix . . . . . . . : custom.domain
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : **custom.domain**

Ethernet adapter vEthernet (cid-54890e7f-6a27-434b-ab4c-12ba9c74c1e6):

Connection-specific DNS Suffix . : **custom.domain**
Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Container Adapter
Physical Address. . . . . . . . . : 00-15-5D-21-52-E4
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::e67b:4cd8:d426:be86%18(Preferred)
IPv4 Address. . . . . . . . . . . : 10.50.130.207(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.50.130.1
DNS Servers . . . . . . . . . . . : **192.168.1.100**
NetBIOS over Tcpip. . . . . . . . : Disabled
Connection-specific DNS Suffix Search List :
**custom.domain**
```

Start by reproducing the supplied dnsPolicy and dnsConfig pod manifest on an EKS 1.30 cluster with Windows EC2 workers and CoreDNS on Fargate, then trace the Windows CNI handling of pod DNS settings. Done means the pod reports 192.168.1.100 as its DNS server and custom.domain as its DNS suffix and search list, matching the expected output.

Written by the indexing model from the issue text.