fix(worker): wire B2 credentials so pending_uploads cleanup cron can run

The new TypeUploadCleanup cron (30 * * * *) constructs a StorageService at
worker startup so it can call b.client.RemoveObject on B2 when reaping
expired pending_uploads rows. Without B2_KEY_ID + B2_APP_KEY the storage
service falls back to local disk and crashes on this pod's read-only
root filesystem, leaving the cleanup as a no-op.

Mirrors the api deployment which already wires these.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

deploy-k3s/manifests/worker/deployment.yaml

@@ -74,6 +74,21 @@ spec:
                   name: honeydue-secrets
                   key: REDIS_PASSWORD
                   optional: true
+            # B2 (Backblaze) credentials. The worker needs these to delete
+            # B2 objects when the pending_uploads cleanup cron reaps
+            # expired upload sessions. Without them the worker falls back
+            # to local-disk storage which fails on this pod's read-only
+            # root filesystem and disables the cleanup cron.
+            - name: B2_KEY_ID
+              valueFrom:
+                secretKeyRef:
+                  name: honeydue-secrets
+                  key: B2_KEY_ID
+            - name: B2_APP_KEY
+              valueFrom:
+                secretKeyRef:
+                  name: honeydue-secrets
+                  key: B2_APP_KEY
             # Observability — workers emit traces (e.g., asynq job spans) to
             # obs.88oakapps.com over OTLP/HTTP. service.name=honeydue-worker
             # so api and worker show up as separate services in Jaeger.