fix(deploy): bump gateway image to sha-9f1a081 (Dockerfile fix from #488)

The fed-v0.1.0-m1 image pin (sha256:9b72e2...) was built before the pnpm
deploy fix in #488 landed. That older image cannot resolve @mosaicstack/
storage at runtime and crashes during bootstrap.

The new digest sha256:1069117740e00ccfeba357cae38c43f3729fe5ae702740ce474f6512414d7c02
was published by Woodpecker pipeline 975 (commit 9f1a0818) using the
corrected Dockerfile and was smoke-tested locally:
  - imports resolve cleanly (no MODULE_NOT_FOUND)
  - bootstrap reaches tier-detector
  - tier detector fails fast with proper error when DB unreachable
  - exits 0 instead of crashing on import

Required to unblock DEPLOY-03/04 (mos-test-1 + mos-test-2 stand-up).

deploy/portainer/federated-test.stack.yml

@@ -30,7 +30,10 @@
 #   DNS A record        ${HOST_FQDN} → Swarm ingress IP (or Cloudflare proxy).
 #
 # IMAGE
-#   Pinned to digest fed-v0.1.0-m1 (DEPLOY-01 verified).
+#   Pinned to sha-9f1a081 (main HEAD post-#488 Dockerfile fix). The previous
+#   pin (fed-v0.1.0-m1, sha256:9b72e2...) had a broken pnpm copy and could
+#   not resolve @mosaicstack/storage at runtime. The new digest was smoke-
+#   tested locally — gateway boots, imports resolve, tier-detector runs.
 #   Update digest here when promoting a new build.
 #
 # NOTE: This is a TEST template — production deployments use a separate
@@ -40,8 +43,8 @@ version: '3.9'
 
 services:
   gateway:
-    image: git.mosaicstack.dev/mosaicstack/stack/gateway@sha256:9b72e202a9eecc27d31920b87b475b9e96e483c0323acc57856be4b1355db1ec
+    image: git.mosaicstack.dev/mosaicstack/stack/gateway@sha256:1069117740e00ccfeba357cae38c43f3729fe5ae702740ce474f6512414d7c02
-    # Tag for human reference: fed-v0.1.0-m1
+    # Tag for human reference: sha-9f1a081 (post-#488 Dockerfile fix; smoke-tested locally)
     environment:
       # ── Tier ───────────────────────────────────────────────────────────────
       MOSAIC_TIER: federated