Migrate ops inventory OCI endpoint to Forgejo registry

Update runtime manifest, event-type example, and resolver test fixture.

event-types/ops-endpoint-verified.md

@@ -45,7 +45,7 @@ non-secret response metadata to the declared expected status and signal.
     "service_id": "gitea",
     "endpoint_id": "gitea-oci-registry",
     "endpoint_type": "https",
-    "endpoint_url": "https://gitea.coulomb.social/v2/",
+    "endpoint_url": "https://forgejo.coulomb.social/v2/",
     "expected_status": 401,
     "status_code": 401,
     "matched_expected_status": true,

k8s/railiance/20-runtime.yaml

@@ -588,7 +588,7 @@ data:
         endpoints:
           - id: gitea-oci-registry
             type: https
-            url: "https://gitea.coulomb.social/v2/"
+            url: "https://forgejo.coulomb.social/v2/"
             expected_status: 401
             expected_signal: "OCI registry auth challenge"
             widget_ref: "ops:endpoint:gitea-registry"

tests/test_ops_inventory_context_resolver.py

@@ -103,7 +103,7 @@ def test_probe_services_marks_status_mismatch_degraded(tmp_path, monkeypatch) ->
     endpoints:
       - id: gitea-registry
         type: https
-        url: "https://gitea.coulomb.social/v2/"
+        url: "https://forgejo.coulomb.social/v2/"
         expected_status: 401
         expected_signal: "OCI registry auth challenge"
     access_paths: []