Fix MCP connector: cert-manager URL typo and TCP probes

Two fixes for the mcp.shorashim.ch deployment:
1. cert-manager ClusterIssuer had acme-v2 (wrong) instead of acme-v02
   (correct). Let's Encrypt ACME directory is at
   https://acme-v02.api.letsencrypt.org/directory
2. gitea-mcp HTTP probes timed out because GET /mcp hangs (SSE).
   Switched to TCP socket probes on port 8080.

MCP server now responds correctly over HTTPS at mcp.shorashim.ch:
  curl -X POST https://mcp.shorashim.ch/mcp -d '{...initialize...}'
  returns {"result":{"serverInfo":{"name":"Gitea MCP Server"}}}

Also: nginx-ingress configmap needed strict-validate-path-type=false
to allow cert-manager HTTP-01 challenges. Applied via kubectl patch,
not tracked in git manifests.

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

deploy/k8s/cert-manager-issuer.yaml

@@ -8,7 +8,7 @@ metadata:
   name: letsencrypt-prod
 spec:
   acme:
-    server: https://acme-v2.api.letsencrypt.org/directory
+    server: https://acme-v02.api.letsencrypt.org/directory
     email: scott@shorashim.ch
     privateKeySecretRef:
       name: letsencrypt-prod-key

deploy/k8s/gitea-mcp-deployment.yaml

@@ -51,14 +51,12 @@ spec:
               memory: "256Mi"
               cpu: "250m"
           livenessProbe:
-            httpGet:
-              path: /mcp
+            tcpSocket:
               port: 8080
             initialDelaySeconds: 10
             periodSeconds: 30
           readinessProbe:
-            httpGet:
-              path: /mcp
+            tcpSocket:
               port: 8080
             initialDelaySeconds: 5
             periodSeconds: 10