…dspeed run`

There previously was a confusion between benchmark name, aka the name
the user gives to individual benchmarks, and benchmark targets.

Now, benchmark target filtering is only done through `--workspace`,
`--package` and `--exclude` cli flags for both `cargo codspeed build`
and `cargo codspeed run`.

In addition, `cargo codspeed run` now properly forwards the `benchname`
positional argument to the benchmark target, in order to filter
benchmarks ran. This is a breaking change, but it makes `cargo-codspeed`
more in line with `cargo bench`

`criterion`'s `Bencher` implements `Send + Sync`, which allows running
the benchmark itself on another thread. This allows something like
`|b| /* my rayon thread pool */.install(|| b.iter(|| /* bench */))`.

cargo-codspeed@4.0.0
codspeed@4.0.0
codspeed-bencher-compat@4.0.0
codspeed-criterion-compat@4.0.0
codspeed-criterion-compat-walltime@4.0.0
codspeed-divan-compat@4.0.0
codspeed-divan-compat-macros@4.0.0
codspeed-divan-compat-walltime@4.0.0

Generated by cargo-workspaces