Auto-start monica_site dj-queue worker on adama (#18)

## Summary
- Closes [#17](#17).
- Django deploy passes optional `host_apps.compose_profiles` as `COMPOSE_PROFILES` so compose profiles survive `up -d --remove-orphans`.
- Adama `monica_site` beta+prod set `compose_profiles: [worker]` (dj-queue singleton). Roslin / ai-server-4080 stay web-only.

## Why
Real campaign sends enqueue dj-queue tasks; without the worker they stay **Queued**. Test email worked because it is synchronous SMTP.

## Test plan
- [ ] Merge + deploy `monica_site` beta (and/or prod) via `deploy.sh`
- [ ] On **adama**, confirm worker container up for `monica_site_beta` / `monica_site_prod`
- [ ] On roslin / ai-server-4080, confirm **no** worker
- [ ] Portal: send campaign → recipient leaves Queued → SentReviewed-on: #18

inventory/group_vars/all.yml

@@ -110,9 +110,8 @@ app_catalog:
     compose_file: docker-compose.prod.yml
     web_service: web
     migrate_cmd: "uv run python manage.py migrate --noinput"
-    # dj-queue worker (compose profile `worker`) is a singleton — start only on
-    # adama after deploy: docker compose -f docker-compose.prod.yml --profile worker up -d
-    # Catalog deploys web + migrate only; worker is manual / ops step.
+    # dj-queue worker = compose profile `worker` (singleton). Deploy starts it
+    # via host_apps.compose_profiles on adama only (see host_vars/adama.yml).
 
 # Deploy filter vars. CI passes these; manual runs may leave them undefined
 # to (re)deploy every app listed in the host's host_apps.