Show changes over time to compiler performance in the triage report

The triage report has improved, but its focus is largely on highlighting single changes impacts on the performance of the Rust compiler. We should think more holistically about what we want to get from the triage report.

Specfically we should add more detail about change over time. For instance, we can show change over the last 1 week/over the period in the triage report, 1 month, 6 months, 1 year, etc.

To do this we can:

• Link to comparison pages that show this difference
• Summarize the difference by showing average percent changes per profile and per scenario (over all benchmarks). Finding the right data to expose here will be a challenge.
• Furthermore, we can highlight changes specifically in real-world benchmarks as this might provide clearer insight over stress tests (which are generally there to prevent regressions)

Start with the triage report and its existing single-change performance views, then inspect the comparison pages and the data available for profiles, scenarios, and benchmarks. Done means the report exposes meaningful change over periods such as a week, month, six months, and a year, including useful summaries or links and clearer insight from real-world benchmarks.