Currently client applications that use transactions may have conflicting non-transactional writes that keep retrying even when no transactions have committed, potentially leading to starvation of the in-progress transaction. For prepare conflicts, we at least block until a prepared transaction has been committed, ensuring forward progress, but for regular conflicts with in-progress transactions we don't.

This ticket is to improve this behavior by having threads with write conflicts wait until they can get a newer snapshot.