[enhancement] improved compare cli output

[gabrielcsapo]

Motivation

When running larger test suites, the CLI output can be very verbose:

Finished 1 of 50 runs.
Finished 2 of 50 runs.
Finished 3 of 50 runs.
Finished 4 of 50 runs.
Finished 5 of 50 runs.
Finished 6 of 50 runs.
Finished 7 of 50 runs.
Finished 8 of 50 runs.
Finished 9 of 50 runs.
Finished 10 of 50 runs.
Finished 11 of 50 runs.
Finished 12 of 50 runs.
Finished 13 of 50 runs.
Finished 14 of 50 runs.
Finished 15 of 50 runs.
Finished 16 of 50 runs.
Finished 17 of 50 runs.
Finished 18 of 50 runs.
Finished 19 of 50 runs.
Finished 20 of 50 runs.
Finished 21 of 50 runs.
Finished 22 of 50 runs.
Finished 23 of 50 runs.
Finished 24 of 50 runs.
Finished 25 of 50 runs.
Finished 26 of 50 runs.
Finished 27 of 50 runs.
Finished 28 of 50 runs.
Finished 29 of 50 runs.
Finished 30 of 50 runs.
Finished 31 of 50 runs.
Finished 32 of 50 runs.
Finished 33 of 50 runs.
..

If we could consolidate the output to the following it would make it a lot easier to gauge what the status of the runs are

Running 1 of 50 (~15 minutes 20 seconds remaining)

duration phase estimated difference -247ms [-292ms to -201ms]
load phase no difference
boot phase estimated difference -191ms [-199ms to -183ms]
transition phase estimated difference -38ms [-57ms to -18ms]
render phase estimated difference -18ms [-33ms to -3ms]
paint phase no difference

The above output would render using something like https://github.com/vadimdemedes/ink to allow the output to constantly change based on the current run.

[lynchbomb]

@gabrielcsapo thanks for the feedback. we will certainly looking into both logging estimated time to complete and a succinct logger.

I know the current implementation is as simple as possible to minimize ambient noise. Assuming we can implement something more robust all while keep noise to an absolute min. sounds-good-to-me.