Find strategy for keeping cargo tooling up-to-date

[ericcornelissen]

Relates to #52, #96, #147

Summary

The project currently uses various cargo-based tools that are tracked and updated manually only, namely:

rust-rm/CONTRIBUTING.md

Lines 114 to 117 in 334a427

	- (Optional) [cargo-all-features] v1.7.0 or later;
	- (Optional) [cargo-deny] v0.14.2 or later;
	- (Optional) [cargo-mutants] v23.5.0 or later;
	- (Optional) [cargo-tarpaulin] v0.25.0 or later;

These tools are also separately tracked in CI workflows (example). Where the CONTRIBUTING.md file is intended to be the minimum version and CI workflows the expected/maximum version.

Tracking these tools in this way is not optimal. It's manual and time consuming, as well as prone to error due to the duplication. Hence this issue.

The ultimate goal is to have a centralized place defining the version of tooling expected to be used that is convenient for contributors and allows for automated updating of tools. Any step in this direction is helpful and worthy of a contribution.

[ericcornelissen]

While I'm not sure if it can be used to keep things up-to-date, the following project looks promising w.r.t. managing the dependencies covered by this issue:

• dustinblackman/cargo-run-bin
• blog post where I found out about it.