Update all Cargo.toml files to use workspace dependency versions

alfiedotwtf commented 3 weeks ago

Description

This PR relates to #6179 which aims to simplify individual workspace member dependency versioning by deferring upstream to the workspace dependencies itself.

I've also extended #6179 as it currently only relates to external dependencies - I've noticed that whenever Sway has a version bump, the diffs manually update all of the many Cargo.toml files to the new globally shared version. We can also use workspaces here to defer each Cargo.toml package version to the workspace package version as well.

This PR is in 3 parts:

Update all Cargo.toml external dependencies to use the shared versions defined in the workspace dependencies
Update all Cargo.toml package version to defer to the workspace package version.
Update all external dependencies to their latest versions

If an individual workspace member needs to break away from the shared workspace package version, we can still do that:

Update the individual Cargo.toml to the new version (as normal)
Update all references within the whole repository to state this new version

Notes:

[dev-dependencies] was not factored out since [workspace.dev-dependencies] is currently not supported by Cargo.toml, meaning all dev dependencies would have to be brought into [workspace.dependencies] which I assume is not what we would want to do.
[target.'cfg(not(target_os = "macos"))'.dependencies] was not factored out since these crates should only be brought in if the condition is met, but again as the only way to do this would be to move it to [workspace.dependencies], I would advise to keep them separated.

Checklist

[✅] I have linked to any relevant issues.
[✅] I have commented my code, particularly in hard-to-understand areas.
[␆] I have updated the documentation where relevant (API docs, the reference, and the Sway book).
- [␆] If my change requires substantial documentation changes, I have requested support from the DevRel team
[␆] I have added tests that prove my fix is effective or that my feature works.
[␆] I have added (or requested a maintainer to add) the necessary Breaking* or New Feature labels where relevant.
[✅] I have done my best to ensure that my PR adheres to the Fuel Labs Code Review Standards.
[✅] I have requested a review from the relevant team or maintainers.