feat(export, viewer): explain summary-maintenance lifecycle decisions

[zzylol]

Stacked on #319.

Why

Operators need to see which summary state is deployed, how it is maintained, why that lifecycle won, and why the alternatives were rejected. Exporting this information without displaying it made lifecycle decisions difficult to inspect.

Before this PR

• DAG export omitted lifecycle guarantees, maintenance modes, alternatives, assumptions, and rejection reasons.
• The DAG viewer could not load a lifecycle-plan export.
• Deployment decisions were not associated with their SummaryAgg nodes.

After this PR

• Lifecycle export includes the selected deployment, maintenance mode, evaluation schedule, output representation, costs, assumptions, and typed rejection reasons.
• The DAG viewer accepts lifecycle-plan JSON and renders it as a single lifecycle lane.
• Selecting a SummaryAgg shows its chosen lifecycle and every considered alternative.
• The selected-node panel preserves the plan-level summary-versus-raw decision, costs, horizon, expected reads, and evaluation/update rates, including when raw recomputation produces no SummaryAgg deployment.

For example, the E2E workload displays a continuously maintained deployment using incremental maintenance. Prepared and Shared remain visible with their rejection reasons.

Visualization

The screenshot below is generated from the lifecycle-plan JSON path implemented by this PR. The selected SummaryAgg shows the winning continuously maintained/incremental contract, plan-level cost and workload evidence, and every considered lifecycle alternative.

Implementation

• Adds the explicitly named summary_maintenance_dag_export mapping adapter.
• Exports lifecycle decisions alongside horizon, demand rates, expected reads, and the raw-recompute comparison.
• Attaches each deployment directly to its exported SummaryAgg; the viewer does not infer identity from labels or graph position.
• Supports lifecycle-plan JSON in both the interactive viewer and standalone HTML renderer.
• Preserves and renders plan-level lifecycle metadata through both viewer ingestion paths.
• Keeps asap-types::dag_export independent of mapping-layer lifecycle policy.
• Tests lifecycle alternatives by kind, node annotations, raw-fallback export, plan-summary loading, and viewer loading.

Verification

cargo test -p asap-integration-tests --test summary_maintenance_lifecycle_e2e
python3 -m unittest discover -s tools/dag-viewer -p test_render.py
cargo clippy -p asap-aware-mapping -p asap-integration-tests --all-targets -- -D warnings

Stack

Base: #319.

[zzylol]

Completed in 42ba08f: the DAG viewer now accepts summary-maintenance plan exports and shows each SummaryAgg deployment selected lifecycle, maintenance mode, schedule, output representation, alternatives, costs, assumptions, and rejection reasons.