Expose minecraft server over TCP via MetalLB

Minecraft Java Edition uses raw TCP on port 25565, not HTTP. The previous
ClusterIP Service + HTTP Ingress (Traefik 80/443) could not carry TCP 25565
traffic, so minecraft.rogi.casa:25565 was unreachable.

- Change Service to LoadBalancer with fixed IP 10.88.20.103 (dmz-pool),
  matching the pihole-dns pattern, so port 25565 is exposed directly.
- Remove the dead HTTP ingress (it routed HTTP to a TCP game port).

minecraft-server/ingress.yaml

@@ -1,24 +0,0 @@
-apiVersion: networking.k8s.io/v1
-kind: Ingress
-metadata:
-  name: minecraft
-  namespace: minecraft
-  annotations:
-    cert-manager.io/cluster-issuer: letsencrypt-prod
-spec:
-  ingressClassName: traefik
-  tls:
-  - hosts:
-    - minecraft.rogi.casa
-    secretName: minecraft-tls
-  rules:
-  - host: minecraft.rogi.casa
-    http:
-      paths:
-        - path: /
-          pathType: Prefix
-          backend:
-            service:
-              name: minecraft-server
-              port:
-                number: 25565

minecraft-server/minecraft-server.yaml

@@ -12,10 +12,12 @@ metadata:
   labels:
     app: minecraft-server
 spec:
-  type: ClusterIP
+  type: LoadBalancer
+  loadBalancerIP: 10.88.20.103
   ports:
     - name: minecraft
       port: 25565
       targetPort: 25565
+      protocol: TCP
   selector:
     app: minecraft-server