cosmic-swingset chain transcript and replay

[mhofman]

What is the Problem Being Solved?

• Ability to replay swingset activity as a whole without requiring tendermint and cosmos. For example this can be useful in evaluating performance issues.
• Verify that the externally observable behavior of swingset execution (data written to vstorage, bank and ibc interactions) is not unexpectedly affected when changing parts of the system that shouldn't affect such execution outcome: liveslots gc, metering, scheduling, XS version (see Acceptance test for new Moddable XS versions #6929)

Description of the Design

A transcript of the bridge interactions between cosmic-swingset and golang cosmos, along with a transcript of the blocking sends received by cosmos. Some parts may need to be captured at a higher level to allow reproducing the semantics of the execution (action queue access, mailbox).

A good start is the old PR doing just this on the pismo chain: #6931

We've since added a lot of features expanding the communication (swing-store export data) as well as narrowing the execution model (run to completion).

Some recent PRs have also introduced refactorings helping layer cosmic-swingset better to be driven without a cosmos side (see #10165)

A nice bonus might also be the ability to use a cosmos state-sync snapshot or genesis export as starting point for the state of a replay (e.g. if vstorage is not strictly checked but instead recreated)

Security Considerations

None, tooling and telemetry only.

Scaling Considerations

Adding this optional feature should not negatively affect the performance of nodes not producing the transcript.

Test Plan

Replay of u17 (including upgrade block)

Upgrade Considerations

Should not be consensus affecting. Need to be able to apply as patch on u17.