Test mainnet configurations for berkeley

[deepthiskumar]

• Run a private network (with berkeley build) with mainnet configurations (mainnet.mlh), and an updated genesis timestamp (to not conflict with current mainnet) and replay a transaction from current mainnet (Not creating a new transaction in this network to avoid being replayed on current mainnet)
• Test ledger hardware?
• Test other signing libraries?

[shimkiv]

The following configuration works well 🎉

• Mina blockchain is formed using artefacts built with the mainnet Dune profile, mainnet genesis configuration is in use, berkeley Mina repository branch (rev:85fc613)
• Ledger Nano X (firmware: 2.2.3)
• Ledger Nano S (firmware: 2.1.0)
• Ledger Mina App v1.0.8
• Auro Wallet v2.2.13 (custom build to match the networkID)

[shimkiv]

Value transfers using latest mina-signer v3.0.0 work well 🎉

[shimkiv]

o1js / zkapp-cli also works 🎉
Fixes required though:

• Add support for mainnet. o1-labs/o1js#1387
• Bump mina-signer and export NetworkId type. o1-labs/o1js#1389
• Missed part of the Mainnet support. o1-labs/o1js#1437
• Fix for Mina-Signer exports. o1-labs/o1js#1442
• Enable custom network signing  o1-labs/o1js#1444
• Missed part of the Mainnet support. o1-labs/o1js-bindings#243
• Introduce the NetworkID parameter for some of the Test.hashFromJson methods. o1-labs/o1js-bindings#244
• Fix createField with non-prime modulus o1-labs/o1js-bindings#246
• Enable custom network signing o1-labs/o1js-bindings#247
• Add support for mainnet. o1-labs/zkapp-cli#564
• Upgrade deps and bump version. o1-labs/zkapp-cli#587