Add project grouping to dashboard

[ClSlaid]

Result

Problem

OpenCode Ensemble currently treats teams as globally scoped in the dashboard and several maintenance paths. That creates two practical issues once a user runs multiple OpenCode instances or works across multiple project directories:

• The dashboard has no project grouping, so teams from different working directories appear in one flat list and same-name teams are hard to distinguish.
• Recovery/cleanup code can accidentally operate across project boundaries because team names were globally unique assumptions in parts of the code.

Solution

• Add a lightweight project layer keyed by the team lead's working directory.
• Scope active team-name uniqueness to project_id instead of globally.
• Return projects[].teams from /api/state while keeping the existing flat teams array for compatibility.
• Add a collapsible docs-style project outline to the dashboard with coarse project/team status and hover details.
• Scope recovery and purge safety checks so duplicate team names across projects do not cause ambiguous cleanup or branch deletion.
• Allow team_create to accept an optional project_name; otherwise generate a short random display name.

Verification

• bun run typecheck
• bun test
• bun run build

[hueyexe]

Ignore the branch name failing check, it's not taking into account a fork.