Deploy Forgejo on railiance01 using gitea-charts/gitea 12.5.0

Pin chart to 12.5.0 because 12.6+ calls `gitea config edit-ini`, which
Forgejo 11 lacks. Ingress targets forgejo-gitea-http (Helm release naming).
Smoke test uses GET for /v2/ registry challenge (HEAD returns 405).

manifests/forgejo-ssh-nodeport.yaml

@@ -0,0 +1,21 @@
+# Git/SSH access for Forgejo (NodePort pattern mirrors coulombcore Gitea).
+apiVersion: v1
+kind: Service
+metadata:
+  name: forgejo-ssh-nodeport
+  namespace: forgejo
+  labels:
+    app.kubernetes.io/name: forgejo
+    app.kubernetes.io/instance: forgejo
+    app.kubernetes.io/part-of: railiance-apps
+spec:
+  type: NodePort
+  selector:
+    app.kubernetes.io/instance: forgejo
+    app.kubernetes.io/name: gitea
+  ports:
+    - name: ssh
+      port: 22
+      targetPort: 2222
+      nodePort: 30022
+      protocol: TCP