Version bump all crate dependencies after the workspace move (#6571)

## Description

This is a continuation of #6179, and follows on from PR #6501. These are
broken into separate PRs so that we can discuss each PR `HEAD`
separately so that the PRs that can get merged, do so quickly.
Otherwise, the further along they get stale the more work they all need
in order to keep up to `master` without being hard to find which change
introduced a possible broken build.

This PR only does a version bump to every crate dependency that does not
need any code changes to apply cleanly.

Following this PR will be a new PR, where every commit updates a single
crate along with the files that were needed to be changed in order to
work again. The crates that will need code changes are:

- tokio 1.12: -> 1.40
- rustc-hash: 1.1 -> 2.0
- miden-core: 0.3 -> 0.10
- notify: 5.0 -> 6.1
- notify-debouncer-mini: 0.2 -> 0.4
- revm: 2.3 -> 14.0
- syn: 1.0 -> 2.0
- tikv-jemallocator: 0.5 -> 0.6
- toml_edit: 0.21 -> 0.22

There should also be a commit to upgrade Rust itself to >= `1.81.0`.

... and for another day, there's 3 crates that will take a bit of time
to get working, and so will go under a different issue #6536:

- annotate-snippets
- lsp-types
- uint

## Checklist

- [x] I have linked to any relevant issues.
- [x] I have commented my code, particularly in hard-to-understand
areas.
- [x] I have updated the documentation where relevant (API docs, the
reference, and the Sway book).
- [x] If my change requires substantial documentation changes, I have
[requested support from the DevRel
team](https://github.com/FuelLabs/devrel-requests/issues/new/choose)
- [x] I have added tests that prove my fix is effective or that my
feature works.
- [x] I have added (or requested a maintainer to add) the necessary
`Breaking*` or `New Feature` labels where relevant.
- [x] I have done my best to ensure that my PR adheres to [the Fuel Labs
Code Review
Standards](https://github.com/FuelLabs/rfcs/blob/master/text/code-standards/external-contributors.md).
- [x] I have requested a review from the relevant team or maintainers.

Co-authored-by: Joshua Batty <[email protected]>