Move repo, CI and the video worker over to the name Feuerwerk (#422)

Stage 3 of the rename. The repo now lives at meleki/feuerwerk, the
runners carry feuerwerk labels and the WSL distro on melektaus-atx is
called feuerwerk-ci. The code has to follow, or CI finds no runner and
the suite no longer picks the GPU path.

- ci.yml: workflow name feuerwerk, jobs on feuerwerk-ci (gate, stein2)
  and feuerwerk-wsl (suite, melektaus-atx).
- GAME_MAKER_* variables are now FEUERWERK_*. This includes
  FEUERWERK_BROWSER=wsl, which the runner config on melektaus-atx sets.
- The video worker runs as container feuerwerk-video with the image
  feuerwerk-video and works on /srv/feuerwerk.
- e2e.sh starts the unit feuerwerk-e2e, the CI image keeps its paths
  under the new name.
- README and repo links point to git.nockal.com/meleki/feuerwerk. The
  old URLs still redirect with 301.

Both runners keep their old labels until the first CI run with this
ci.yml is through. Then they go, together with the image tag
game-maker-ci:latest and GAME_MAKER_BROWSER in the atx config.

Tests:
- Gate on melektaus-atx through the renamed distro: CHECK EXIT 0,
  307 files, 4756 tests.
- e2e 60 on melektaus-atx: ALL PASSED, 20 checks. Renderer is the
  RTX 4070 through D3D12, so FEUERWERK_BROWSER reaches the GPU path.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

.gitea/workflows/ci.yml

@@ -1,10 +1,10 @@
 # Runs the whole proof on the Gitea runner: gate, the editor suite and the three example games.
 #
-# The suite runs on `game-maker-wsl`, the runner in the WSL2 distro game-maker-ci on
+# The suite runs on `feuerwerk-wsl`, the runner in the WSL2 distro feuerwerk-ci on
 # melektaus-atx (#283). Its label picks the image built from tools/ci/Dockerfile. The GPU
-# (/dev/dxg and the Windows driver libraries), /dev/shm and GAME_MAKER_BROWSER=wsl come from that
+# (/dev/dxg and the Windows driver libraries), /dev/shm and FEUERWERK_BROWSER=wsl come from that
 # runner's own config.yaml, not from here – without them chromium falls back to software WebGL and
-# the harness stops. The gate needs no GPU and runs on `game-maker-ci`, the runner on stein2 with
+# the harness stops. The gate needs no GPU and runs on `feuerwerk-ci`, the runner on stein2 with
 # the same image. Pointing the suite at that label too moves the browser runs back to stein2.
 #
 # Two jobs without `needs:`, so they start together. The gate does not stand in front of the
@@ -14,7 +14,7 @@
 # On two runners the gate's vitest no longer shares cores with the suite's chromium, which
 # measures text widths and frame counts. GM_TEST_WORKERS still caps vitest at two workers, for the
 # day both jobs share one runner again.
-name: game-maker
+name: feuerwerk
 
 on:
   push:
@@ -22,7 +22,7 @@ on:
 
 jobs:
   gate:
-    runs-on: game-maker-ci
+    runs-on: feuerwerk-ci
     timeout-minutes: 20
     steps:
       - uses: actions/checkout@v4
@@ -46,7 +46,7 @@ jobs:
           php tests/php/videos.test.php
 
   suite:
-    runs-on: game-maker-wsl
+    runs-on: feuerwerk-wsl
     timeout-minutes: 45
     steps:
       - uses: actions/checkout@v4