Measure the dashboard performance impact on k6

[oleiade]

As part of our goal to have the web dashboard activated by default within k6, we need to measure and quantify the performance impact of the dashboard in k6.

To do so, we would like to compare the performance of k6 from the memory and computation perspective in a context where the dashboard is active and disabled.

We might want to leverage the k6-benchmarks to do that.

The expected outcome of this would be to have reasonably reliable comparison data of k6 running with and without the dashboard enabled to decide whether or not there is an overhead and if we're accepting to pay the price of it.