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/backend-ci.yml

@@ -15,6 +15,7 @@ on:
       - "server/scripts/**"
       - "server/Dockerfile"
       - "server/.dockerignore"
+      - ".gitea/workflows/backend-ci.yml"
   pull_request:
     branches:
       - main
@@ -29,6 +30,7 @@ on:
       - "server/scripts/**"
       - "server/Dockerfile"
       - "server/.dockerignore"
+      - ".gitea/workflows/backend-ci.yml"
   workflow_dispatch:
 
 permissions:
@@ -88,7 +90,7 @@ jobs:
           REGISTRY_USERNAME: root
           REGISTRY_PASSWORD: ${{ secrets.REGISTRY_PASSWORD }}
           REGISTRY_PLAIN_HTTP: "true"
-          IMAGE_LIST: migrate tenant-api ops-api worker-generate kol-assist-worker scheduler
+          IMAGE_LIST: migrate tenant-api browser-fetch ops-api worker-generate kol-assist-worker scheduler
           DELETE_OLD_IMAGE_TAGS: "true"
         run: |
           set -eu