Support Mesa upgrade

[dannywillems]

The list is available here: https://www.notion.so/o1labs/Hard-Fork-MIPs-Project-1c9e79b1f910805fb44cdc2b9db2ee8e?p=1c9e79b1f910804da24ed4f96638ab2b&pm=s.

For each feature, an issue should be opened, and should be linked as a sub-issue.
For instance, #1261 has been opened for the "Events and Accounts limit update" MIP, and has been set a sub-issue.

Each issue should contain a link to the list of patches on the OCaml node that implements the feature.
While working on an issue, the assigned person should ensure that the documentation is updated accordingly, and a page listing the patches for each feature should be added. This single page will gather all the changes, with links to MIPs, OCaml patches and Rust patches.
If an issue is related to a part of the codebase that is not documented, the assigned person is responsible to add documentation beforehand. It is recommended to use an AI assistant (Claude or Copilot, but no strong preferences) to automatically generate the documentation by providing either the specification from the Mina Protocol website or the OCaml codebase. An example can be found in #1263.

For each issue, the patches should include performance improvements and tests. The benchmark should be added in a benchmark sub-directory. The tests should include at least the ones implemented in the OCaml node. For instance, #1261 should include benchmark as the MIP mentions that they won't be any performance regression. The test plan for the performance should be well documented, and the CI should continuously compile the code to ensure it is still runnable. Continously publishing the benchmarks are not part of individual issues.

TBD:

• design a way to support network, protocol and cryptography breaking changes in the codebase. Using two different branches is a solution, but not viable for the long term.