Allow "time compression" for large swaths of time.

This is just a random thought, it would perhaps improve UX.

You have two traces from the same machine, one when things were working well, one where things degraded.

The views may have 2 seconds of data in the beginning, followed by 3 hours of empty space, and 2 seconds of data in the end.

This is an example of the proposed view.


No file, test, or entry point is named. Start by reading the traceviewer-base and traceviewer-react-components libraries, focusing on how timeline data is rendered; define the behavior and validation needed for compressing empty time spans before implementation can begin.

Written by the indexing model from the issue text.