feat: NV23 Waffle support 🧇

[LesnyRumcajs]

Summary of changes

💛 Sorry for a relatively large PR, I was not confident in the changes until they were all working together with a NV23-compatible Lotus.

Changes introduced in this pull request:

• FIP-0085 migration,
• FIP-0091 consensus implementation,
• Butterflynet, Devnet and Calibnet upgrade with required bundles and assets,
• Introduced a common type for EthChainId to unify it's usage,
• integrated v14 actors,
• renamed Aussie to Waffle as the network upgrade codename

Reference issue to close (if applicable)

Closes #4366
Part of #4318

Other information and links

Tests done on:

• 2k network (as part of the CI),
• Butterflynet (with https://github.com/filecoin-project/lotus/tree/aarsh-butterfly-updated-assets-NV23-RC1). I managed to send a transaction with Coinbase Wallet (it uses legacy EIP-155 transactions) that got correctly recorded on chain, Forest still follows the chain.

TODO

• Assert correct calibnet state after the upgrade,

# Lotus v1.28.0-rc.1
2024-07-04T15:24:04.479+0200    WARN    statemgr        stmgr/forks.go:211      COMPLETED migration     {"height": "1759060", "from": "bafy2bzacebop56rpqe3ag6fwwzuqiktjdlfkutxbpuhvucyjeugwezvj22ypq", "to": "bafy2bzaceb7wforg3w3g4sauo6vn6gtmon74jegjjv4quvxnuxe326dhr2tqo", "duration": 0.437529503}

# Forest
2024-07-04T13:23:41.775935Z  INFO compute_tipset_state_blocking: forest_filecoin::state_migration: State migration at height Waffle(epoch 1759060) was successful, Previous state: bafy2bzacebop56rpqe3ag6fwwzuqiktjdlfkutxbpuhvucyjeugwezvj22ypq, new state: bafy2bzaceb7wforg3w3g4sauo6vn6gtmon74jegjjv4quvxnuxe326dhr2tqo, new state actors: bafy2bzaceaem6dns4klmosw5be5rbodyqfkrieeg65rhouj7eivawqqiejzoq. Took: 0.677725s.

• Legacy Ethereum transactions on Butterflynet - Homestead, EIP-155 and EIP-1559 are correctly identified and consensus was held after tests with FilOz.
• Cleanup code, add more tests for legacy Ethereum transactions.
• Add relevant docs and links
• Prepare a release + comms (follow-up)

Change checklist

• I have performed a self-review of my own code,
• I have made corresponding changes to the documentation,
• I have added tests that prove my fix is effective or that my feature works (if possible),
• I have made sure the CHANGELOG is up-to-date. All user-facing changes should be reflected in this document.