Point issue-core ArgoCD Application at Forgejo Git source

ArgoCD was still tracking gitea.coulomb.social, which lags Forgejo after the
registry migration. Sync issue-core workload manifests from forgejo.coulomb.social
so backend ConfigMap updates land on CoulombCore.

Also allow forgejo.coulomb.social in railiance-tenants AppProject sourceRepos.

argocd/applications/issue-core.application.yaml

@@ -11,7 +11,7 @@ metadata:
 spec:
   project: railiance-tenants
   source:
-    repoURL: https://gitea.coulomb.social/coulomb/issue-core.git
+    repoURL: https://forgejo.coulomb.social/coulomb/issue-core.git
     targetRevision: main
     path: k8s/railiance
   destination:

argocd/bootstrap/01-railiance-tenants-project.yaml

@@ -10,6 +10,7 @@ spec:
   description: Guardrails for Railiance tenant applications deployed by ArgoCD.
   sourceRepos:
     - https://gitea.coulomb.social/coulomb/*.git
+    - https://forgejo.coulomb.social/coulomb/*.git
   destinations:
     - server: https://kubernetes.default.svc
       namespace: "*"

argocd/repositories/issue-core.repository.sops.yaml.template

@@ -15,7 +15,7 @@ metadata:
 stringData:
   type: git
   project: railiance-tenants
-  url: https://gitea.coulomb.social/coulomb/issue-core.git
+  url: https://forgejo.coulomb.social/coulomb/issue-core.git
   username: CHANGE_ME
   password: CHANGE_ME