One can select which benchmark (pystone, numpy, matplotlib, or all) to be run through command-line arguments.
We can divide each benchmark to separate CI jobs in the future if needed.
Moved pystone benchmark to benchmark directory, preventing it from being included in Pyodide release.
* benchmark html5 canvas renderer
* adhere to lint
* rectify condition
* increase timeout
* do suggested changes
* adhere to lint
* use correct backend for benchmarks
* reintroduce tests + fix futures callback
* adhere to lint
* increase timeout for tests
* use selenium_standalone for tests
* increase timeout for check_comparison
* add result() to Future
* add debugging print statement
* adhere to lint
* use draw() instead of draw_idle()
* add new reference image for math text
* return NaN for non-native
* replace math text image for chrome as well
* increase timeout
* selenium standalone for benchmarks
* only matplotlib benchmarks
* re-enable benchmarks for numpy
* adhere to lint
* increase timeout