Running cargo semver-checks with no other arguments should default to checking

[era]

Addresses #414.

It allows users to run cargo semver-checks without using the subcommand check-release.

I basically moved CheckRelease to be a field at SemverChecks.

I tried to also remove it from the SemverChecksCommands::CheckRelease enum by using global = true on all fields from CheckRelease, but I could not add that property to manifest and workspace fields.

I reused the tests from feature_config to make sure the same use cases work when user specifies the subcommand or not.

[obi1kenobi]

Love the tests, great idea to use the existing test setup to ensure this functionality works too!

Just a few minor suggestions for further improvement.

[obi1kenobi]

Could we refactor the code here a bit to avoid the duplicated logic?

Maybe something like:

let check: cargo_semver_checks::Check = args.command.unwrap_or_else(|| args.check_release.into());

let report = check.check_release()?;
// ...

[obi1kenobi]

This duplication is a bit unfortunate: over time as we edit these tests and add new ones, we might update one version of the check but fail to update the other. This is a maintainability risk.

Could you think of another way to set up the test where we don't need to duplicate all the test code like this? Perhaps by doing some more refactoring of the CargoSemverChecks type?

[era]

Let me know if the tests are better now, I thought of adding an assert(fn(Assert) -> ()) -> () function to CargoSemverChecks, but I was not sure if exposing the vector wouldn't be the best move.

Also, not sure about the way I remove the subcommand from args. Let me know if you think it could be better.

[obi1kenobi]

Nicely done! A couple of tiny tweaks and this is good to go 🚀

[era]

Thank you again @obi1kenobi for all the reviews!

[obi1kenobi]

Awesome, let's ship it 🚀