Feat/nv21 migrations optimized tree diff algorithm

[snissn]

Related Issues

#11071

Proposed Changes

• Imported v12 of the filecoin state types in migrations.go. This allows the system to interpret and operate on the latest structure of filecoin state information, ensuring compatibility with the latest version of the Filecoin network.

• Updated the 'getMigrationFuncsForNetwork' function to include a case for network.Version21, enabling the use of the UpgradeActorsV12 and PreUpgradeActorsV12 functions for network migration. These changes ensure the system correctly handles migrations when the network upgrades to version 21.

• Include latest version of go-state-types module which includes optimizations for AMT diffing, allowing this migration to happen swiftly

• Added a new 'pprof' flag to the command-line arguments in main.go. This flag allows the user to specify a file name for writing CPU profile information, enabling performance analysis.

• includes skeleton nv21 migration kit which need to be filled out by @ZenGround0 and @arajasek

Additional Info

This has been benchmarked and the optimization for AMT diffing has been verified to be correct via correct stateroot cids.

REMINDER: If you are running this, you likely want to ALSO run the continuity testing tool!
manifest cid: bafy2bzacedowjygm2fy5yryyyjcww6znqngoz4rildgouuj6uk35z7a2u5gmc
migration height  3104159
old cid  bafy2bzacebap5x7ow7xwubdnqfodveuksbp4k63oe7f6ukl752cm3vtp5m7fo
new cid  bafy2bzaced3m4tbxhq5fcybisppaiafbnguwecjxhkn46jds7y75yimrfc2vq
completed round actual (without cache), took  11m49.470263157s
manifest cid: bafy2bzacedowjygm2fy5yryyyjcww6znqngoz4rildgouuj6uk35z7a2u5gmc
completed premigration, took  10m20.103971889s
manifest cid: bafy2bzacedowjygm2fy5yryyyjcww6znqngoz4rildgouuj6uk35z7a2u5gmc
completed round actual (with cache), took  15.86165313s
Ec2 Instance Type - i4i.4xlarge
lotus branch - feat/nv21-migrations-optimized-tree
worker count - num-cpus

below without optimizations in go-state-type version:

REMINDER: If you are running this, you likely want to ALSO run the continuity testing tool!
manifest cid: bafy2bzacedowjygm2fy5yryyyjcww6znqngoz4rildgouuj6uk35z7a2u5gmc
migration height  3104159
old cid  bafy2bzacebap5x7ow7xwubdnqfodveuksbp4k63oe7f6ukl752cm3vtp5m7fo
new cid  bafy2bzaced3m4tbxhq5fcybisppaiafbnguwecjxhkn46jds7y75yimrfc2vq
completed round actual (without cache), took  16m12.368587429s
manifest cid: bafy2bzacedowjygm2fy5yryyyjcww6znqngoz4rildgouuj6uk35z7a2u5gmc
completed premigration, took  15m33.544663821s
manifest cid: bafy2bzacedowjygm2fy5yryyyjcww6znqngoz4rildgouuj6uk35z7a2u5gmc
completed round actual (with cache), took  1m43.923645056s
Ec2 Instance Type - i4i.4xlarge
lotus branch - feat/nv21-migrations-perf
worker count - num-cpus

Checklist

Before you mark the PR ready for review, please make sure that:

• Commits have a clear commit message.
• PR title is in the form of of <PR type>: <area>: <change being made>
  • example: fix: mempool: Introduce a cache for valid signatures
  • PR type: fix, feat, build, chore, ci, docs, perf, refactor, revert, style, test
  • area, e.g. api, chain, state, market, mempool, multisig, networking, paych, proving, sealing, wallet, deps
• New features have usage guidelines and / or documentation updates in
  • Lotus Documentation
  • Discussion Tutorials
• Tests exist for new functionality or change in behavior
• CI is green

[arajasek]

LGTM -- there's a couple more checks I'd like to add, happy to push a commit to this branch or have that be a separate PR.

Thank you!

[snissn]

Hey! It'd be a lot simpler for me if we could land this PR then create your check as additional work in a new PR