No transaction in TaskRunRecorder

[zzstoatzz]

related to #16299

in the TaskRunRecorder we call record_task_run_event which performs

• an insert of the task run where the state timestamp is newer
• an insert of the task run state
• an update of the task run where the timestamp is non-existent or older than the current state's timestamp

record_task_run_event wraps these statements in a transaction, but these operations should be idempotent. In the interest of speeding up the many writes that may occur when running task-heavy flows, this PR removes begin_transaction=True

[codspeed-hq]

CodSpeed Performance Report

Merging #16829 will not alter performance

_{Comparing no-transaction (8ddf45f) with main (753ae01)}

Summary

✅ 2 untouched benchmarks

[chrisguidry]

Yep, I'm pretty confident about this one. In Prefect Cloud (which does have some slightly different transactional semantics), these are independent statements not in a transaction either. In the case of errors or message replays, the final system state should still be coherent.

[cicdw]

Tests related to this change are failing - does this change require an explicit session.commit() call?

[zzstoatzz]

Tests related to this change are failing - does this change require an explicit session.commit() call?

@cicdw looking now!