per-crate versions

[zeroXbrock]

Motivation

Each crate was deriving its version from the workspace, but crates have their own dependency graphs and locally- (or downstream)-breaking changes that may not reflect the CLI (the binary release).

Making a breaking change in contender_core doesn't mean that the cli has a breaking change. To the cli, that's a patch.

for example: the current unreleased set of changes includes one breaking feature in contender_core, but it doesn't actually affect the code in contender_cli. So contender_core should switch to v0.11.0 and contender_cli (because it relies on contender_core but doesn't introduce any breaking changes to its users) should switch to v0.10.1 (which will happen in a PR following this one).

Solution

• version each crate independently; stop using version.workspace = true
• revise the release scripts (remove script 1 and update script 2) to create tags for individually versioning crates
• update the release workflows to account for the new tag scheme

PR Checklist

• Added Tests
• Added Documentation
• Ran cargo +nightly clippy --workspace --lib --examples --tests --benches --all-features --locked --fix
• Ran cargo fmt --all
• Note breaking changes in PR description, if applicable
• update changelogs
  • Update CHANGELOG.md in each affected crate
  • add a high-level description in the root changelog