There are various times in the codebase where we try to maintain the durable state and the in-memory state in sync.

One such example is the CollectionCatalog, where we go to great lengths recreating atomic commit semantics between durable and in-memory changes.

This also is relevant whenever a point in time read is performed, as usually those times we need to either reconstruct the in-memory state from the durable content or to maintain some form of timestamp awareness in the global in-memory state.

This ticket is about providing a new primitive constructed on top of WT such that we can maintain an in-memory state in lock-step with the durable state.