fix: revert resolver timeouts (#7883)

This wasn't needed for the 502 on Pythia, even though the ingress-nginx
controller does set resolver timeouts, let's not do this now.

Author: agoose77

helm-charts/basehub/values.yaml

@@ -13,8 +13,6 @@ binderhub-service:
     annotations:
       nginx.ingress.kubernetes.io/proxy-body-size: 256m
       cert-manager.io/cluster-issuer: letsencrypt-prod
-      nginx.org/server-snippets: |
-        resolver_timeout 30s;
   nodeSelector:
     hub.jupyter.org/node-purpose: core
   service:
@@ -438,8 +436,6 @@ jupyterhub:
       nginx.org/location-snippets: |
         proxy_set_header Upgrade $http_upgrade;
         proxy_set_header Connection $connection_upgrade;
-      nginx.org/server-snippets: |
-        resolver_timeout 30s;
       cert-manager.io/cluster-issuer: letsencrypt-prod
   scheduling:
     # We declare matchNodePurpose=require to get a nodeAffinity like a