Describe the problem

If there is a retry error on statement execution, the default behaviour of the workload is to rollback the transaction. However, if there are any savepoints in the transaction (which might occur due to op generation failures), then
we observe a ERROR: restart transaction: TransactionRetryWithProtoRefreshError: cannot rollback to savepoint after a transaction restart (SQLSTATE 40001).

Expected behavior
The workload can expect this error by keeping track of if savepoints have been set in the txn so that it does not fail due to an unexpected error. Alternatively, we can add some logic to create a new txn instead of rolling back when retry errors are seen.

Additional Notes
This issue was observed in these roachtest failures:

• roachtest: scbench/randomload/nodes=3/ops=10000/conc=20 failed #56230 (comment)
• roachtest: schemachange/random-load failed #56235 (comment)
• roachtest: schemachange/random-load failed #56235 (comment)