Check execution trace differences for v16

[arajasek]

We have a new stream of execution trace info with v16 as we upgrade to the FVM. While care has been taken to make sure the same amount of information is captured, there may be unintended changes in the format / shape of the returned information.

We should remove any such changes if possible -- ideally the output of exec traces with the FVM will be identical to the current output we get on the LegacyVM. This way we guarantee no UX issues arising from the v16 changes, as users won't observe any difference.

[arajasek]

Suggested approach:

• Replay an "interesting" message on the v16 caterpillarnet / butterflynet, getting its execution trace. Anything that involves (at least) one internal message is a good fit -- I think PreCommitSector (with deals), ProveReplicaUpdates, DisputeWindowedPost could all be good choices, as well as the implicit Cron call to the power actor.
• Replay the same message type on mainnet / calibnet today
• Compare and contrast the outputs. Anything trivially different between should be fixed to be the same. Anything non-trivial might need discussion.
• Do the same, but this time grabbing the HTML and JSON outputs. Make sure they're well-formed (and essentially the same) as the LegacyVM.

[arajasek]

We should also test an MsigAprrove, since that is the message that's most relevant to our known users of this feature.

[geoff-vball]

Note: In nv16, subcall exec traces are no longer populated by default, to get the previous behaviour you must set the env var LOTUS_VM_ENABLE_TRACING=1 (this was formerly LOTUS_VM_ENABLE_GAS_TRACING_VERY_SLOW.

One small change was made in #8804 to make the exec traces line up.