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/host_vars/roslin.yml

@@ -13,6 +13,6 @@ host_apps:
   - { name: chat_web_app, env: beta, port: 8083 }
   - { name: chat_backend, env: prod, port: 8003 }
   - { name: chat_backend, env: beta, port: 8013 }
+  # monica_site worker NOT here — adama host_apps sets compose_profiles: [worker].
   - { name: monica_site, env: prod, port: 8004 }
   - { name: monica_site, env: beta, port: 8014 }
-  # monica_site worker is NOT on roslin — singleton on adama only.