ntwk v17 migration integration and testing

[jennijuju]

• Update go-state-types

• Migration Integration
  This will be something of a living issue -- as we develop nv17, we will have various changes to go-state-types that we'll need to integrate into Lotus (eg FIP-0041: Introduce new types go-state-types#52, FIP-0034: Modify the types for v9 go-state-types#53, FIP-0029: Add & modify types for v9 go-state-types#54).
  Each integration will likely involve work to Lotus's state abstractions as well.

• rerunning the migration using lotus-shed with the latest RC

• Ensuring correctness and that it's fast enough

• Running the migration in "online" mode -- this means letting the premigration happen while the lotus daemon is syncing the chain, making sure the time and memory usage are okay

• Param finalization: based on time and memory usage of the experiments, we need to settle on the correct number of and epochs for premigration

[arajasek]

The migration is now fully integrated, and testing has begun in #9446. Here is a list of further assertions we should make:

• that for each pending, verified deal in v8 market, there is a corresponding allocation in v9 verifreg Allocations
• that nextAllocationID is equal to the number of pending, verified deals in v8 market
• that for each pending, verified deal in v8 market, there is a corresponding entry in v9 market PendingDealAllocationIds
• that all miners that have PreCommits with deals in them have non-nil UnsealedCid, and this CID is correctly calculated:
  • IMPORTANT: Perform this calculation using the FFI's GenerateUnsealedCID. This will help us test the correctness of the new go-based CommD calculator that the migration is using.

[jennijuju]

@arajasek did we do

Running the migration in "online" mode -- this means letting the premigration happen while the lotus daemon is syncing the chain, making sure the time and memory usage are okay ?