chore(cargo-codspeed): bump cargo to 0.75

[art049]

Fixes #29

[codspeed-hq]

CodSpeed Performance Report

Merging #31 will not alter performance

_{Comparing bump-cargo (750e29a) with main (fc75139)}

Summary

✅ 54 untouched benchmarks

[davidhewitt]

@art049 is it necessary to build cargo into this package? Most other cargo subcommands I'm aware of use cargo as a CLI subprocess, e.g.

https://github.com/flamegraph-rs/flamegraph/blob/3c9d14643335db861521af1f66e1c2f9eb5aaf56/src/bin/cargo-flamegraph.rs#L89
https://github.com/taiki-e/cargo-llvm-cov/blob/0a65263bdafa3b72a26cf15c2e1c3410738df649/src/main.rs#L356

The downside of building cargo into the package like this is that it creates a mismatch between whatever Rust toolchain is installed and the bundled cargo version. This means that cargo-codspeed is currently missing the sparse registry and I worry it may have other bugs or subtle incompatibilities with the local Rust toolchain.

[art049]

@davidhewitt I think it's not necessary. At some point, it could have been interesting to "hot" replace the benchmark library and avoid using our compatibility layers. We haven't given it an in-depth look yet, so we're unsure if it would be possible.

But yes, definitely using the cargo CLI directly would make things simpler.

[art049]

Supersed by #43