Use latest proof-systems/master in Mina

[dannywillems]

TODO:

• remove 2ebba30
• remove aa565a4
• fix nix
• Build o1js + o1js-bindings (Compatibility with !16464 on Mina o1-labs/o1js#1990 and Compatibility with !16464 on Mina o1-labs/o1js-bindings#330)
• remove nightly in CI - see follow-up CI: remove Rust nightly. Not used anymore. #16533
• write a script to verify that the versions used in proof-systems/Cargo.toml matches the ones used at the top-level of this repository. See Add a script to check that proof-systems deps are up-to-date with root Cargo.toml #16526.

---

Revamping #16405. Note that this PR targets fix/compatibility, waiting for a fix in o1js.

This pull request has as a first goal to update Mina to use the master branch of proof-systems, instead of develop (which is going to be deleted when the related o1-labs/proof-systems#2868 is merged).

Reviewers can follow commits by commits. The commits are ordered in a way to understand the thought process.
Run these commands to check the build works locally:

git clone https://github.com/MinaProtocol/mina/ /tmp/test-mina
cd /tmp/test-mina
git submodule update --init --recursive
opam switch create ./ 4.14.0
eval $(opam env)
opam switch import opam.export
./scripts/pin-external-packages.sh
dune build src/lib/crypto
dune runtest src/lib/crypto
dune runtest src/lib/pickles
# cleaning and rebuilding.
dune clean
cargo clean
dune build src/lib/crypto

In addition to making the code in kimchi-bindings/stubs and kimchi-bindings/wasm compatible with the latest version of proof-systems, this work re-organizes the management of the Rust dependencies between the different Rust crates. Subsequent works will move all the Rust code into proof-systems (see the WIP o1-labs/proof-systems#2875 and o1-labs/proof-systems#2876).

Currently, the Rust dependencies of proof-systems/develop and the Rust dependencies involved in the crates kimchi-bindings/stubs and kimchi-bindings/wasm are separated. When doing this work, I encountered multiple conflicting version dependencies, which made the work more complicated to deliver. Therefore, I decided:

• to keep proof-systems as a submodule (even though in the history there is an attempt to use it as a direct dependency).

• to use Cargo workspaces to manage the dependencies of kimchi-bindings/stubs and kimchi-bindings/wasm together, in addition to proof-systems. It is done by defining once and for all the versions of the dependencies in a top-level Cargo.toml. The Cargo.toml in kimchi-bindings/stubs and kimchi-bindings/wasm. As proof-systems is a submodule, and defines also a workspace, we have to ignore it in the top-level Cargo.toml, and copying the dependencies required by proof-systems at the top-level Cargo.toml is required. A script checking that the versions are the same is in progress here.

• to get rid of nightly for wasm. When trying to vendor the dependencies, I realized that it wasn't possible to vendor the std (required as we do build-std=panic_abort,std). I end up realizing that using nightly wasn't required, as already noticed in Rust 1.74 o1-labs/proof-systems#2875, and we could simply use the same Rust version).

• to vendor all dependencies to keep a consistent Rust environment, coined "mina-rust-dependencies", managed as a submodule this time. It is mostly proof-systems-vendor renamed, and updated. A related PR exists here for compatible. We might need to create multiple branch later.

• to add a Makefile target to (re-)vendor the Rust dependencies, update-rust-dependencies.

The cargo workspace will probably disappear soon as we're moving the Rust code in proof-systems.

[dannywillems]

!ci-build-me

[dannywillems]

!ci-build-me

[dannywillems]

Converting to draft while fixing nix.

[dannywillems]

!ci-build-me

[dannywillems]

!ci-build-me

[dannywillems]

!ci-build-me

[volhovm]

Compiles well now 🎉

Only has some minor warnings: the config key profile.release.target one and the one on the screenshot:

[dannywillems]

Do not merge, please. Fixing o1js/o1js-bindings first.

[dannywillems]

I updated the o1js/bindings PR dep:

Build o1js + o1js-bindings (o1-labs/o1js#1990 and o1-labs/o1js-bindings#330)

[dannywillems]

Closing as @mrmr1993 updated in #16614. This PR does a bit more like using a single Cargo.toml and trying to get rid of nightly. Not a priority. Keeping in mind if we move everything into proof-systems.