Fix/cargo workspace deps version for publishing

[vemilano]

Description

This PR makes 2 things:

1. Fixes CRASH on cargo provider #2001. Commitizen was crashing when a workspace member had a fixed version
2. Add support for rust projects with workspace members that want to publish their crates on crates.io

Regarding the second point, to provide more details, crates.io requires that each crate have a version specified in Cargo.toml. For projects that use a workspace, this means that all members using version.workspace = true must also have a version specified at the workspace.dependencies level (the specified version must be the same as that of workspace.version).

When performing a version bump, in addition to updating workspace.version (in Cargo.toml) and the versions in Cargo.lock, we must also update the versions specified in Cargo.toml, since they are actually dynamically managed by Cargo via version.workspace = true.

Projects such as crate-ci/cargo-release or pksunkara/cargo-workspaces also use the same process

Checklist

• I have read the contributing guidelines

Was generative AI tooling used to co-author this PR?

no

Code Changes

• Add test cases to all the changes you introduce
• Run uv run poe all locally to ensure this change passes linter check and tests
• Manually test the changes:
  • Verify the feature/bug fix works as expected in real-world scenarios
  • Test edge cases and error conditions
  • Ensure backward compatibility is maintained
  • Document any manual testing steps performed
• Update the documentation for the changes

[codecov]

⚠️ JUnit XML file not found

The CLI was unable to find any JUnit XML files to upload.
For more help, visit our troubleshooting guide.

[vemilano]

I checked the fix for #2001 proposed by pull request #2002 and preferred to keep the fix I'm proposing in that pull request. The merged fix introduces a regression, since the try: expect: NonExistentKey block was removed, even though the "version" key is optional for a package.

@bearomorphism @Lee-W @woile , do you know if a review of this pull request is planned? Until it's merged, it's not possible to publish to crates.io with commitizen in a Rust project with a workspace.

To recall the objective of this PR, a project may have a Cargo.toml like this:

[workspace]
members = ["members/*"]
resolver = "2"

[workspace.package]
edition = "2024"
version = "0.1.0"

[workspace.dependencies]
member-hello = { path = "members/hello" }

And the Cargo.toml of the workspace member:

[package]
name = "member-hello"
version.workspace = true

In order to publish on crates.io (cargo publish --workspace), every dependency MUST have a specified version, so we need something like:

[workspace.dependencies]
member-hello = { path = "members/hello", version = "0.1.0" }

But this version is dynamically resolved (because the workspace member has version.workspace = true). So when we want to cz bump:

• bump workspace version
• update versions in Cargo.lock
• update the "version" key for workspace dependencies that have a version specified and match a member inheriting (and handle potentially renamed deps)