ci(deploy): correct deploy runner label to uom-deploy-runner

The deploy job referenced a runner labelled `uom_deploy`, which doesn't
match the actual self-hosted runner (`uom-deploy-runner`), so the job
would queue forever waiting for a runner that never picks it up. Update
the `runs-on` label (and the two doc comments) to the real label.

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

.gitea/workflows/build-images.yml

@@ -5,13 +5,13 @@
 # Two jobs run in sequence:
 #   build   — builds & pushes website-app / website-bot images (on ubuntu-latest)
 #   deploy  — `needs: build`, so it starts only after a clean build+push, and
-#             pulls + recreates the stack on the production host (on uom_deploy)
+#             pulls + recreates the stack on the production host (on uom-deploy-runner)
 #
 # Prerequisites (one-time):
 #   • An always-on Gitea runner with label `ubuntu-latest` whose jobs have the
 #     host Docker socket mounted (/var/run/docker.sock), so `docker build` talks
 #     to the host daemon. This also gives free layer caching between runs.
-#   • A second self-hosted runner labelled `uom_deploy` ON the production host,
+#   • A second self-hosted runner labelled `uom-deploy-runner` ON the production host,
 #     with access to the Docker daemon and to /home/perry/website (the directory
 #     holding the production docker-compose.yml + .env). This is what actually
 #     rolls the stack; it must be able to `docker compose pull` from the registry
@@ -102,7 +102,7 @@ jobs:
     # this wait for a clean build+push — if the build fails, deploy never fires,
     # so the running stack is left untouched rather than torn down for nothing.
     needs: build
-    runs-on: uom_deploy
+    runs-on: uom-deploy-runner
     # Guard against a workflow_dispatch fired from a non-main branch: only ever
     # deploy the main line to production.
     if: github.ref == 'refs/heads/main'