Pin inter crate dependencies to specific version

[ascjones]

Raised by @deuszx.

Currently dependencies between the ink crates are specified with a range i.e. 4.2.0 which means >= 4.2.0, <5.0.

This means that when we released 4.2.1 recently, and contracts with an ink dependency of 4.2.0 could pull in the new versions sub crates.

This PR pins the versions of the inter-crate dependencies of all the ink crates, since they are always released together.

[deuszx]

If they are always released together - you can consider switching to cargo workspace dependencies features and specify it (version, authors, etc.) in root Cargo.toml.

[ascjones]

If they are always released together - you can consider switching to cargo workspace dependencies features and specify it (version, authors, etc.) in root Cargo.toml.

Good idea. I think @HCastano was investigating this at some point but not sure how far he got.

Issue: #1814

[codecov-commenter]

Codecov Report

Merging #1813 (3c33996) into master (14c850c) will increase coverage by 0.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #1813      +/-   ##
==========================================
+ Coverage   52.14%   52.16%   +0.01%     
==========================================
  Files         206      206              
  Lines        6656     6656              
==========================================
+ Hits         3471     3472       +1     
+ Misses       3185     3184       -1     

see 1 file with indirect coverage changes

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

[xgreenx]

It creates conflicts for #1835, but them is not hard to solve. I think we can start with pinning the version without a workspace, and when PR is ready switch to the workspace approach