kvserver: unhandled TransactionPushError when push finds STAGING but known-uncommitted Read Committed transaction #105330
Description
Describe the problem
In #97779 we're introducing reproposals and reproposal errors in kvnemesis.
For some reason, under stress, kvnemesis will now sometimes find a *TransactionPushError bubble up from db.Get and db.Scan (and likely other methods), which should not be possible.
@arulajmani is looking at this in https://cockroachlabs.slack.com/archives/G01G8LK77DK/p1687356168950489.
Jira issue: CRDB-28983