Replace AbstractFateStore.verifyReserved() with new method FateMutator.requireReserved()

[Amemeda]

Add new method to FateMutator.java that requires a FateId to be reserved for certain transactions. This method will replace AbstractFateStore.verifyReservedAndNotDeleted() implementation in UserFateStore.java.

• Added FateMutator.requireReserved() and its implementation in FateMutatorImpl.java. requireReserved() requires a transaction to be reserved with a specific FateStore.FateReservation.
• Removed usages of verifyReservedandNotDeleted() from UserFateStore.java methods. To replace its implementation, new method requireReserved() called through new helper method newReservedMutator in push(), pop(), setStatus(), setTransactionInfo(), delete(), and forceDelete(). For methods top(), getStack(), getTransactionInfo(), and timeCreated(), verifyReservedandNotDeleted() simply was removed since it is a no-op.

Closes #4908

[Amemeda]

(OUTDATED)
Since verifyReservedAndNotDeleted() was removed from UserFateStore.java, new requireReserved() was implemented in its place on the FateMutator side. However, in 4 UserFateStore.java methods (top, getStack, getTransactionInfo, timeCreated) there is no corresponding fateMutator method being called where requireReserved() should be added. Unsure how to replace implementation for these 4 methods.

[dlmarion]

Changes look good, I kicked off a full IT build to see if this causes any failures.

[dlmarion]

UserFateIT_SimpleSuite.testNoWriteAfterDelete failed. Please run locally to see if you can reproduce the failure and fix.

[Amemeda]

I was able to reproduce the failure. The test was only failing on assertThrows(Exception.class, txStore::pop);, so updated UserFateStore.pop() by moving the create a new reserved fate mutator outside of the top.ifPresent(...), but kept the deleteRepo and mutate:

FateMutator<T> fateMutator = newReservedMutator().requireStatus(REQ_POP_STATUS.toArray(TStatus[]::new)); top.ifPresent(t -> fateMutator.deleteRepo(t).mutate());

The push method right above handles this the exact same way, the failing test is now passing locally.