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/nas-compose-service-deploy.yml

@@ -11,6 +11,7 @@ on:
         options:
           - frontend
           - ops-web
+          - browser-fetch
           - tenant-api
           - ops-api
           - worker-generate
@@ -296,6 +297,9 @@ jobs:
             ops-web)
               service_list="ops-web"
               ;;
+            browser-fetch)
+              service_list="browser-fetch"
+              ;;
             tenant-api)
               service_list="tenant-api"
               auto_migrations=true
@@ -320,11 +324,11 @@ jobs:
               service_list="frontend ops-web"
               ;;
             backend)
-              service_list="tenant-api ops-api worker-generate kol-assist-worker scheduler"
+              service_list="tenant-api browser-fetch ops-api worker-generate kol-assist-worker scheduler"
               auto_migrations=true
               ;;
             all-apps)
-              service_list="tenant-api ops-api worker-generate kol-assist-worker scheduler frontend ops-web"
+              service_list="tenant-api browser-fetch ops-api worker-generate kol-assist-worker scheduler frontend ops-web"
               auto_migrations=true
               ;;
             *)