Console web: retire legacy Scope-as-Team home components

[potter-sun]

Background

Legacy Team home components still encode current-session-team and Scope-as-Team assumptions. Keeping them around increases the chance that future work reuses old semantics.

Scope

• Confirm whether LegacyTeamsHome, TeamsHomeRosterV0, and shared legacy helpers are still referenced.
• Remove unused legacy Team home components and tests.
• If any path still depends on them, replace the dependency with the real Team roster surface.

Acceptance Criteria

• No unused legacy Team home component remains in the console web source tree.
• No active route or feature flag points to a Scope-as-Team home surface.
• Typecheck/build remains clean after cleanup.

[potter-sun]

Implementation batch: Batch 4 / cleanup. Do after the canonical Team route and P1 user path settle, then remove legacy Scope-as-Team surfaces only if no active route or flag depends on them.