workflows: use LAN registry endpoint for push (CF 100MB cap)

Cloudflare in front of git.jpaul.io caps HTTP request bodies at
100 MB, which kills container blob pushes for our 6 GB image
(Chroma layer alone is ~2 GB). Per the template gotcha doc:

  Push via LAN endpoint (192.168.0.2:1234, plain HTTP, in the
  Gitea host's insecure-registries list).
  Pull via public hostname (git.jpaul.io) — pull response bodies
  aren't capped.

REGISTRY_PUSH:  192.168.0.2:1234
REGISTRY_PULL:  git.jpaul.io   (unchanged; used for the package-link API)

This matches how hvm-docs / morpheus-docs / opsramp-docs / zerto-docs
CI workflows push successfully on the same Gitea host.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

.gitea/workflows/image-only.yml

@@ -21,7 +21,7 @@ on:
       - "sources.json"
 
 env:
-  REGISTRY_PUSH: git.jpaul.io
+  REGISTRY_PUSH: 192.168.0.2:1234
   REGISTRY_PULL: git.jpaul.io
   IMAGE: ${{ github.repository_owner }}/${{ github.event.repository.name }}
   OLLAMA_URL: http://192.168.0.2:11434,http://192.168.0.2:11435,http://192.168.0.125:11434

.gitea/workflows/refresh.yml

@@ -27,7 +27,7 @@ on:
 
 env:
   # Self-hosted Gitea registry on the same LAN as the runner.
-  REGISTRY_PUSH: git.jpaul.io
+  REGISTRY_PUSH: 192.168.0.2:1234
   REGISTRY_PULL: git.jpaul.io
   IMAGE: ${{ github.repository_owner }}/${{ github.event.repository.name }}