Race between RegionRemoteProcedureBase and rollback operation could lead to ROLLEDBACK state be persisent to procedure store

And then cause load procedures failure.

This is because we do not execute RegionRemoteProcedureBase.persistAndWake method in PEWorker, so even if we hold the procedureExecutionLock in rollback, they could be executed concurrently.

So it is possible that in rollback, we set the state to ROLLEDBACK and delete the procedure, and then in persistAndWake, we persist the ROLLEDBACK state to procedure store.