Improve release procedure

[chrisjsewell]

Currently, cargo release minor will dry-run through and update all packages to a new version,
but then warn e.g. updating xxx to 0.2.0 despite no changes made since tag xxx-v0.1.0.
Then you can decide which packages to release individually, and what type of version bump (major/minor/patch)

Ideally, there would be one command that

1. would not release unchanged packages (unless there were changes to dependent packages)
2. Could independently decide which version bump type, per package

[chrisjsewell]

Possibly related to crate-ci/cargo-release#688, crate-ci/cargo-release#298 and pksunkara/cargo-workspaces#4