Fix server names to match gluetun's ProtonVPN server list

US-TX#253 and US-TX#34 aren't in gluetun's built-in list. Switching to:
- Main qbt: US-IL#149 (was US-IL#267)
- Fornax TX253: US-TX#179
- Fornax TX34: US-TX#220
Private keys are per-account and work with any ProtonVPN WireGuard server.

servers/legion/k8s/media/fornax-workers.yaml

@@ -51,9 +51,9 @@ spec:
                 secretKeyRef:
                   name: fornax-worker-tx253-secrets
                   key: PROTONVPN_PRIVATE_KEY
-            # Pin to US-TX#253 from gluetun's built-in ProtonVPN server list
+            # US-TX#179 — from gluetun's built-in ProtonVPN server list
             - name: SERVER_NAMES
-              value: "US-TX#253"
+              value: "US-TX#179"
             # gluetun handles NAT-PMP internally, exposes port at :8000/v1/openvpn/portforwarded
             - name: VPN_PORT_FORWARDING
               value: "on"
@@ -200,8 +200,9 @@ spec:
                 secretKeyRef:
                   name: fornax-worker-tx34-secrets
                   key: PROTONVPN_PRIVATE_KEY
+            # US-TX#220 — from gluetun's built-in ProtonVPN server list
             - name: SERVER_NAMES
-              value: "US-TX#34"
+              value: "US-TX#220"
             - name: VPN_PORT_FORWARDING
               value: "on"
             - name: FIREWALL_OUTBOUND_SUBNETS

servers/legion/k8s/media/gluetun-qbittorrent.yaml

@@ -45,9 +45,9 @@ spec:
                 secretKeyRef:
                   name: media-secrets
                   key: PROTONVPN_PRIVATE_KEY
-            # Pin to US-IL#267 (NAT-PMP enabled per ProtonVPN portal)
+            # US-IL#149 — from gluetun's built-in ProtonVPN server list
             - name: SERVER_NAMES
-              value: "US-IL#267"
+              value: "US-IL#149"
             # gluetun handles NAT-PMP exchange natively for protonvpn provider
             - name: VPN_PORT_FORWARDING
               value: "on"