fix(stack): group database helper containers with their stack

[avallete]

Summary

TL;DR: This builds on #6867, which groups a stack's containers as one compose project in Docker Desktop and OrbStack. The database storage helper containers (supabase-db-helper-*) were still left outside that group. They now join their stack's compose project as the database-helper service.

Stacked on #6867; merge that first.

Before

flowchart LR
  G["Compose project supabase-myapp-…"] --> S["studio, rest, database …"]
  H["supabase-db-helper-…"] --> U["Ungrouped in Docker Desktop/OrbStack"]

Loading

After

flowchart LR
  G["Compose project supabase-myapp-…"] --> S["studio, rest, database …"]
  G --> H["supabase-db-helper-…<br/>service: database-helper"]

Loading

What changed

• A shared composeProjectFor in runtime/ContainerName.ts derives the compose project for both the stack's service containers and its helpers.
• The database storage receives the project folder name. Both the per-instance helper and the shared volume helper get com.docker.compose.project and com.docker.compose.service=database-helper.
• Helper names and existing com.supabase.* labels are unchanged. Helpers carry no com.supabase.service label, so service log collectors skip them.

Linked issue

None.

🤖 Generated with Claude Code

[github-actions]

🤖 AI Review

Both independent reviews reported no findings. I checked the changed code and its surrounding call paths and found no actionable issue: database containers and storage helpers use the same compose project name, and the helper labels are applied on both creation paths.

Findings

No issues found.

Stats

Claude findings: 0 · Codex findings: 0 · Confirmed: 0 · Refuted: 0 · Uncertain: 0

---

Models: claude-opus-5-5 + gpt-6-sol · Trigger: auto · Workflow run

This review runs once per PR. A maintainer can request another with a /ai-review comment.