ci: add versions to cargo workspace

[sdankel]

Description

This should unblock releases. Cargo doesn't use the workspace version for path dependencies, so we still have to specify the versions. This is also how it's done in fuel-core.

This is actually nice because it means we could in the future bump the versions of the dependencies separately, all from within the one file.

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.