visualizer: render multi-component (monorepo) pipelines

[joshua-temple]

Problem

A multi-component (monorepo) manifest defines several independently versioned components that
share environments. The visualizer must render each component's lane, the shared environments,
and the per-component flows so a reader can see how the components move together and apart.

Cross-cutting dependency

This issue depends on the component model existing. It builds on the schema_version 1
component model: the Components map[string]ComponentConfig, ComponentState, and
ComponentReleaseState shapes (formerly reserved under #176) are now live and carry behavior.
This work renders that model.

Tracked under the monorepo epic #279. This issue depends on #279, and #279 should link back
to this issue as the visualizer slice of monorepo support.

Approach (once the model is live)

• One lane/subgraph per component (Mermaid subgraph), each carrying that component's
  build/deploy flow.
• Shared environments rendered once, with per-component promotion edges into them, so the
  shared-vs-independent structure is visible.
• Honor the chosen granularity per component (jobs/stages/env).

Tests (TDD)

• Golden Mermaid for a two-component manifest sharing environments: assert a lane per component
  and shared-environment nodes referenced by both.
• Determinism.
• An e2e/ scenario for a multi-component manifest.

Acceptance

• A multi-component manifest renders each component's lane, the shared environments, and the
  per-component flows.

Dependencies

#301, #303, and the schema_version 1 component model from monorepo epic #279 (hard blocker).

[joshua-temple]

This is the visualizer's schema-2 rendering slice. It is deliverable only inside the
monorepo/schema-2 work, so it is tracked in the monorepo milestone and unblocks once #279
lands.