When we are applying a prepared transaction and are in recovery or initial sync, we set roundUpPrepareTimestamps to true on the recovery unit.

Then, when we go to unstash the transaction resources and start the transaction, we call _setReadSnapshot. There, if we see the catalog has changed while we were allocating the storage snapshot, we abandon the snapshot.

Abandoning the snapshot instructs the recovery unit to close the transaction, which resets the value of _roundUpPreparedTimestamps to kNoRound.

Then, when we go to prepare the transaction with the timestamp behind stable, we find the round-up setting is unexpectedly not set, which causes WiredTiger to invariant. (As of SERVER-86763 we invariant a bit sooner because we added an assertion earlier on to try to help diagnose this case.)

We should fix this to ensure that we preserve this setting.