ci(browser-fetch): include browser-fetch image in build and deploy pipelines

Add browser-fetch to backend-ci image list, NAS compose/K3s deploy options
and rollout loops, and the offline package bundle so the new service ships
through the same pipelines as the rest of the backend.

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

.gitea/workflows/offline-package.yml

@@ -53,7 +53,7 @@ jobs:
       REGISTRY_USERNAME: ${{ inputs.registry_username }}
       REGISTRY_PASSWORD: ${{ secrets.REGISTRY_PASSWORD }}
       REGISTRY_PLAIN_HTTP: ${{ inputs.registry_plain_http }}
-      IMAGE_LIST: migrate tenant-api ops-api worker-generate kol-assist-worker scheduler frontend ops-web
+      IMAGE_LIST: migrate tenant-api browser-fetch ops-api worker-generate kol-assist-worker scheduler frontend ops-web
     steps:
       - name: Checkout
         uses: actions/checkout@v4