Move dependencies into workspace

[fridrik01]

This PR moves all dependencies and metadata (version, license, etc) to the root workspace so that we can manage them in a central place.

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (a8f9be1) 75.79% compared to head (534e7c5) 75.59%.
Report is 3 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #1955      +/-   ##
==========================================
- Coverage   75.79%   75.59%   -0.20%     
==========================================
  Files         157      157              
  Lines       15441    15490      +49     
==========================================
+ Hits        11703    11710       +7     
- Misses       3738     3780      +42     

see 8 files with indirect coverage changes

[Stebalien]

Ah.... I think this may have been why we didn't include this in the workspace. We need to check the cargo tree (and enabled features) in the workspace itself to make sure we're not "unifying" them. I'll go ahead and do that.

[Stebalien]

Basically, look up "feature unification in rust" if you want to have bad dreams.

[Stebalien]

Hm. Actually... this seems fine? I thought I saw the arbitrary feature/crates getting included in the main dependency tree... but now I'm not seeing that.

[Stebalien]

Ok, so, I think this actually works. But is there any reason not to migrate the rest of the deps (e.g., wat in the integration tests, the rest of the fvm dependencies, etc.

Are we just moving "shared" deps?

[fridrik01]

Ok, so, I think this actually works. But is there any reason not to migrate the rest of the deps (e.g., wat in the integration tests, the rest of the fvm dependencies, etc.

Are we just moving "shared" deps?

Yeah, I skipped moving dependencies that only were used in one crate into the root workspace