chore: move dev dependencies to workspace

[sdankel]

Description

Moves dev dependencies to the workspace Cargo.toml for consistent versions in tests.

Inspired by #6955

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.

[codspeed-hq]

CodSpeed Performance Report

Merging #6966 will not alter performance

_{Comparing sophie/dev-dep-workspace (bddc310) with master (1c3183a)}

Summary

✅ 22 untouched benchmarks

[zees-dev]

LGTM 👍

Minor improvement commented on the previous PR: #6955 (comment)
Not required though.

[sdankel]

LGTM 👍

Minor improvement commented on the previous PR: #6955 (comment) Not required though.

Apparently workspace members can only inherit workspace dependencies, not dev dependencies (even as dev dependencies). I can't find it in the documentation anywhere, but if you try adding it to a dev-dependencies section in the root Cargo.toml, and use workspace = true in a member manifest, you'll see an error like:

dependency.wiremock` was not found in `workspace.dependencies`

[zees-dev]

LGTM 👍
Minor improvement commented on the previous PR: #6955 (comment) Not required though.

Apparently workspace members can only inherit workspace dependencies, not dev dependencies (even as dev dependencies). I can't find it in the documentation anywhere, but if you try adding it to a dev-dependencies section in the root Cargo.toml, and use workspace = true in a member manifest, you'll see an error like:

dependency.wiremock` was not found in `workspace.dependencies`

Interesting I did not know about this; thanks!