[5/x][lamport] Remove SequenceNumber::decrement and ::increment

[amnn]

SequenceNumber::decrement is used primarily to revert state
updates (e.g. when an update crosses an epoch or configuration change
and then needs to be rolled back).

With the introduction of lamport timestamps, this will no longer be
feasible with decrement, because a transaction can increment an
object's version by an arbitrary amount (not always one), depending on
the versions of other input objects.

This commit re-implements revert_state_update to rely on a list of
initial versions for modified inputs that gets stored in
TransactionEffects and gets rid of the decrement API altogether.

increment is replaced by two pieces:

• SequenceNumber::lamport_increment to calculate a lamport timestamp.
• SequenceNumber::increment_to to increment to a number that should
  be strictly greater than the current version.

And now, rather than objects being incremented when they are modified,
versions are updated as follows:

• Shared object scheduling pre-computes their new versions based on
  the transaction's inputs.
• The TemporaryStore is aware of the lamport timestamp for the
  transaction it's serving, and assigns all modified objects (this
  includes inputs and child objects) this version when committing
  modifications to effects.
• We also remember the versions modified and deleted objects had,
  in case we need to revert -- we can't rely solely on the information
  from the certificate for this, because we could have dynamically
  loaded child objects which need to be reverted as well.

Gateway also needs some special support in order to replay
certificates: Previously it took the objects that were indicated as
modified in effects and replayed those modifications into a store, but
new protections that this commit introduces to ensure that all objects
get incremented would complain (because the objects in the effects
come with thei post-modified version), so before replaying the
modifications, the gateway will decrement an object's version to their
pre-modified state, as specified by modified_at_versions in effects,
using a new SequenceNumber::decrement_to API.

Test Plan

cargo simtest
cargo nextest run

[tnowacki]

Things look mostly good! At a high level, I'm wondering if things would be simpler if we just put all logic for versioning to the layer outside of the adapter.

[tnowacki]

Should we just remove the sequence number from new_coin?

[amnn]

Yeah, this is one of the clean-ups I want to do after the fact. In the limit, the version could maybe even be moved entirely out of MoveObject as well (so the store becomes solely responsible for handling it, and move and the adapter layer are completely unaware.

[amnn]

Thanks for the reviews both! Agreed that with us dropping support for owned to shared upgrades, all the logic can now be moved out of the adapter, which is nice! I'll rebase and make those changes.

[tnowacki]

Thanks for doing this! I think it's finally good to go!