Move SealShare from GitHub to Gitea only

The workflows live in .gitea/workflows. The Docker workflow logs in to
the Gitea container registry with REGISTRY_TOKEN (Gitea's job token cannot
publish packages yet), publishes gitea.nonameweb.ch/nonameweb/sealshare
with a registry build cache, and makes the release on Gitea with the
version's section of the changelog as its notes.

The README, the website's quick start, both compose files and the image
label point to Gitea; the changelog announces the new image name and
links Gitea. GiteaOnlyTest keeps GitHub and ghcr.io out.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01V9NnLxnPp8vaaurb3Z1MFy

website/index.html

@@ -547,11 +547,11 @@
         <div class="code">
             <div class="code__bar"><svg class="icon" aria-hidden="true"><use href="#i-terminal"/></svg><span>Production, with Docker Compose</span></div>
 <pre><code>mkdir sealshare &amp;&amp; cd sealshare
-curl -O https://raw.githubusercontent.com/surtic86/SealShare/main/docker-compose.example.yml
+curl -O https://gitea.nonameweb.ch/noNameWEB/SealShare/raw/branch/main/docker-compose.example.yml
 cp docker-compose.example.yml docker-compose.yml
 
 <span class="comment"># Generate an app key and paste it into docker-compose.yml</span>
-docker run --rm ghcr.io/surtic86/sealshare:latest php artisan key:generate --show
+docker run --rm gitea.nonameweb.ch/nonameweb/sealshare:latest php artisan key:generate --show
 
 <span class="comment"># Edit docker-compose.yml — set APP_KEY, APP_URL, and SERVER_NAME</span>
 <span class="comment"># Then start:</span>