fix: explicitly set resolver version in virtual manifest (lambdaclass…

…#1311)

* Explicitly set resolver version in virtual manifest

The default for crates with edition >= 2021 is the version 2 of the resolver.
Virtual manifests, however, default to version 1.
Seems that when we moved the VM to its own directory, we also changed the resolver we used.

* Update changelog

---------

Co-authored-by: Pedro Fontana <fontana.pedro93@gmail.com>

CHANGELOG.md

@@ -2,9 +2,12 @@
 
 #### Upcoming Changes
 
+* fix: specify resolver version 2 in the virtual workspace's manifest [#1311](https://github.com/lambdaclass/cairo-vm/pull/1311)
+
 * feat: add `lambdaworks-felt` feature to `cairo-vm-cli` [#1308](https://github.com/lambdaclass/cairo-vm/pull/1308)
 
-* chore: update dependencies, particularly clap 3.2 -> 4.3
+* chore: update dependencies, particularly clap 3.2 -> 4.3 [#1309](https://github.com/lambdaclass/cairo-vm/pull/1309)
+
   * this removes dependency on _atty_, that's no longer mantained
 
 * chore: remove unused dependencies [#1307](https://github.com/lambdaclass/cairo-vm/pull/1307)

Cargo.toml

@@ -2,6 +2,10 @@
 members = ["cairo-vm-cli", "felt", "vm", "hint_accountant"]
 exclude = ["ensure-no_std"]
 
+# Explicitly set the resolver to the default for edition >= 2021
+# https://doc.rust-lang.org/edition-guide/rust-2021/default-cargo-resolver.html
+resolver = "2"
+
 [workspace.package]
 version = "0.8.1"
 edition = "2021"