Cleanup request creation should be state-independant.

Currently the cleanup request creation requires the current state of the transaction in order to be registered. While this makes sense in the case of the mutations list, this introduces an issue since its possible that the state of the transaction has been changed by an external actor. We should update cleanup not to rely on the state at time of registration and instead fetch the state from the ATR. I'm also curious if there is an additional race here where a transaction could be stuck ambiguous and then cleanup starts removing staged contents while another process is trying to commit them.