upstream(core): Track and store unchanged loaded runtime objects

[jkrvivian]

Description of change

• Port commit:
  • MystenLabs/sui@89b03a8
  • MystenLabs/sui@feaeb1f
• Description:

This patch implements tracking of unchanged loaded runtime objects and
stores this information in the perpetual store. This is done so that we
can package up a checkpoint that includes full information necessary to
either perform any analysis based on the objects read or written by a
transaction or to efficiently replay a transaction without needing to
fetch any additional objects (except packages).

The tracking is done by wrapping the BackingStore that is provided to
the VM with one that tracks and saves all objects that were loaded
during execution. This is more accurate than the existing
"loaded_runtime_objects" structure returned from the execution layer
since it also will capture things like the coin deny list.

In addition to this a new Checkpoint structure is introduced that is
intended to eventually replace the existing CheckpointData structure.
This new type is intended to only be used in-memory (if you need a
persisted structure the proto version of the message should instead be
used) and it explicitly does not implement Serialize/Deserialize so that
it cannot be accidentally be persisted.

Links to any relevant issues

Fixes #12459

How the change has been tested

• Basic tests (linting, compilation, formatting, unit/integration tests)
• Patch-specific tests (correctness, functionality coverage)
• I have added tests that prove my fix is effective or that my feature works
• I have checked that new and existing unit tests pass locally with my changes

Not ported: client-facing gRPC exposure

• Upstream also serves the tracked data over gRPC: a new effects.unchanged_loaded_runtime_objects proto field in GetTransaction responses, and checkpoint responses whose objects are built from the new complete object set.
• This requires proto additions in iota-grpc-types and ledger service changes (upstream got the field via a sui-rust-sdk bump), so it is deferred to a follow-up. Until then the data is tracked and stored, but not served to clients.
• Upstream's e2e test suite for the feature (unchanged_loaded_runtime_objects.rs) asserts those gRPC fields, so it is deferred together with the exposure work.

[jkrvivian]

Close bc we don't need to port the full feature to fix this issue. It'll be fixed in https://github.com/iotaledger/iota/pull/12698/changes