Fix 503 error by moving ingress to neonvortex namespace

The ingress was still in the default namespace trying to route
to a service that no longer exists there. Moved ingress to the
neonvortex namespace where the service actually resides.

Fixes: 503 Service Unavailable error
Tested: https://nv.caffeinetux.com now returns HTTP 200

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>

neon-vortex-ingress-neonvortex.yaml

@@ -0,0 +1,25 @@
+apiVersion: networking.k8s.io/v1
+kind: Ingress
+metadata:
+  name: neon-vortex
+  namespace: neonvortex
+  annotations:
+    cert-manager.io/cluster-issuer: letsencrypt-prod
+    nginx.ingress.kubernetes.io/ssl-redirect: "true"
+spec:
+  ingressClassName: nginx
+  rules:
+  - host: nv.caffeinetux.com
+    http:
+      paths:
+      - path: /
+        pathType: Prefix
+        backend:
+          service:
+            name: neon-vortex
+            port:
+              number: 80
+  tls:
+  - hosts:
+    - nv.caffeinetux.com
+    secretName: neon-vortex-tls