Migrate to cargo criterion

[saik0]

https://github.com/bheisler/cargo-criterion

• cargo-criterion seeks to improve iteration time for Criterion-rs benchmarks. By moving functionality into a separate executable which can be installed once and reused, Criterion-rs can shrink - meaning less code to compile and link into the benchmarks themselves.
• Because cargo-criterion can oversee the whole benchmark process from beginning to end, it's better placed to deliver features that would be difficult to implement in Criterion-rs. These include:
  - Machine-readable output
  - Tracking benchmarked performance over time

This is fantastic. Want. In addition to the above we can get rid of html-reports feature of criterion and bench will have much few dependencies -> faster CI builds.

[Kerollmops]

In addition to the above we can get rid of html-reports feature of criterion and bench will have much few dependencies

What do you mean by get rid of it? Do you mean that we will reduce our set of dependencies but will we keep the HTML reports? I hope so as they were easy to read, crawl, and understand.

[saik0]

Right. cargo-criterion can generate all the reports. criterion can just be "just" the benchmark runner.

The idea is to have fewer build-deps for projects that use criterion, since it's lifted out to the cargo-criterion binary.