ci: point deploy pipeline at moby/brewlog after repo move

The repo moved from the uberbau owner to moby on the zo forge. Update
the image registry path and Kaniko git context accordingly.

.github/workflows/deploy.yml

@@ -1,5 +1,5 @@
 name: Build & Publish
-# Fork build pipeline for the "zo" forge (git.ziemlichoptimal.de/uberbau/brewlog).
+# Fork build pipeline for the "zo" forge (git.ziemlichoptimal.de/moby/brewlog).
 # On every push to `dev` this checks the code, then builds the container and
 # publishes it to this forge's own container registry. The moby homelab
 # (git.ziemlichoptimal.de/moby/cluster-moby) deploys the resulting image via
@@ -23,7 +23,7 @@ permissions:
 env:
   # This forge's built-in container registry, same host as the git server.
   REGISTRY: git.ziemlichoptimal.de
-  IMAGE: git.ziemlichoptimal.de/uberbau/brewlog
+  IMAGE: git.ziemlichoptimal.de/moby/brewlog
 
 jobs:
   check:
@@ -87,7 +87,7 @@ jobs:
       - name: Build and push (Kaniko)
         env:
           # Forgejo auto-provides GITHUB_TOKEN; it can push packages for this
-          # repo's owner (uberbau) and read this (private-context) git repo.
+          # repo's owner (moby) and read this (private-context) git repo.
           FORGE_USER: ${{ github.actor }}
           FORGE_TOKEN: ${{ secrets.GITHUB_TOKEN }}
           # Kaniko reads these to clone the `--context` git URL.
@@ -103,7 +103,7 @@ jobs:
           # like checkout). `dev` is the moving branch tag; the commit SHA is the
           # immutable ref the moby Deployment pins by digest.
           /kaniko/executor \
-            --context "git://${REGISTRY}/uberbau/brewlog.git#refs/heads/dev" \
+            --context "git://${REGISTRY}/moby/brewlog.git#refs/heads/dev" \
             --dockerfile Dockerfile \
             --destination "${IMAGE}:${GITHUB_SHA}" \
             --destination "${IMAGE}:dev"