ci: no workflow builds --profile ai; m175, m85, m159, m177 run in no workflow #183

The README claims modules whose gates run in no workflow, and no groot workflow builds the AI profile that four claimed AI modules need.

Evidence

• grep -l "<gate>-" .github/workflows/* apps/grobase/.github/workflows/* at groot develop (grobase pin 6f533a18) matches nothing for:
  • m175: collab namespace isolation (README row 3, WebSockets)
  • m85: tenant observability (Prometheus + Grafana, not claimed)
  • m159: storage bucket scope (file upload, not claimed)
  • m177: self-serve apps (row 13, the free-choice major)
• grep -n -- '--profile' .github/workflows/*: only graph-studio.yml:69 builds, with --profile dev. Nothing builds or starts --profile ai. The osionos side is tested only in osionos CI (AI service (tsc + suite)), against the service alone.

Asked

1. A workflow job that runs docker compose --profile ai build (and ideally up + one /api/ai/health check) on groot PRs that touch the pin or docker-compose.yml.
2. m175 and m177 in a workflow, because they back claimed rows. m85 and m159 are needed before Prometheus/Grafana or file upload can be claimed.

Context: #182 (README Modules table with the CI job per row), #171.

Refs #155