Add regression escape tracker dashboard

[maziyarpanahi]

Description

Adds a metric-only regression-escape tracker over ordered benchmark release history. It distinguishes regressions stopped by release gates from regressions that shipped, records the release and elapsed time when escaped regressions recover, and exposes deterministic JSON plus a self-contained HTML dashboard for release-readiness review.

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update
• Code refactoring
• Test addition/improvement

Changes Made

• Compare each suite and flattened metric against the last shipped benchmark report, classifying regressions as gated, escaped, or recovered.
• Add release-readiness JSON with open-escape counts, recovery timing, and deterministic recurring-regression hotspot ranking.
• Add a self-contained HTML dashboard and privacy guards that omit source metadata and sanitize non-technical identifiers.

Testing

• I have added tests that prove my feature works.
• New and existing unit tests pass locally with my changes.
• I have tested this change with multiple suites, metric directions, gate outcomes, release sequences, and unsafe metadata.
• .venv/bin/python -m pytest tests/ -q — 5196 passed, 55 skipped.

Documentation

• I have updated the documentation accordingly.
• I have added docstrings to new functions/classes.
• I have updated the CHANGELOG.md.

No user-facing documentation or changelog update is required for this focused evaluation API addition.

Code Quality

• I ran make format, make lint, and make format-check.
• For Swift/OpenMedKit changes, I ran make format-swift and make lint-swift.
• I have performed a self-review of my own code.
• I have commented the code where the release-history behavior is non-obvious.
• My changes generate no new warnings.
• Scoped mypy and pre-commit checks pass.

Dependencies

• I have not added any new dependencies.
• OR I have added new dependencies and they are justified because: N/A

Checklist

• I have read the contributing guidelines.
• My commit has a clear, descriptive message.
• I have organized the commit appropriately.

Related Issues

Closes #936

Screenshots/Examples

The dashboard output is covered by deterministic, balanced-HTML, self-contained-asset, and no-raw-PHI tests.