Features used by the compiler might cause version conflicts when bumping compiler

[gabrielbosio]

Cairo Compiler uses Cairo VM as a dependency (See Link).

Because Cairo VM also uses the Compiler as a dependency, this might cause version conflicts when trying to bump the Compiler.

We need to:

1. Check if changing the Compiler version results in conflict versions. Also check if changing the version of a dependency both the VM and the Compiler uses also causes in a version conflict.
   a. If yes, go to 2.
   b. If not, we can consider this issue as completed.
2. Check what features of the VM are being used by the Compiler. Investigate if these features can be moved into another crate or repo.

[DiegoCivi]

Tried bumping the compiler to 2.12.3 both in main and in v2.5.0 (cairo 2.12.3 uses vm 2.5.0) and there where no conflicts. Although the VM uses the compiler and the compiler is used in the VM, there is no cyclic dependency because of how cargo resolves dependencies. Right now we have the following:

cairo-vm (local)
  └── cairo-lang-starknet
        └── cairo-lang-compiler
              └── cairo-lang-runnable-utils
                    └── cairo-vm (crates.io)

But this does not generate any errors since one VM is the "local" one and the other is from crates.io.

Also checked what would happen if we bump the common dependencies between the VM and the compiler. The only dependency that generated conflicts in this case was the one of the rand crate