Add JDBC transaction recovery for JVM and native scenarios

[michalvavrik]

Summary

Adds transaction recovery test coverage for native and JVM. OpenShift will require changes in Test Framework that I didn't really explore yet. IMHO there is plenty of changes already and we should wait for OCP. DEV mode is something that is worth to do (especially due to quarkusio/quarkus#34576 (comment)), but not part of original test plan here https://github.com/quarkus-qe/quarkus-test-plans/blob/main/QUARKUS-2739.md and I didn't get to it yet.

Please select the relevant options.

• Bug fix (non-breaking change which fixes an issue)
• Dependency update
• Refactoring
• Backport
• New scenario (non-breaking change which adds functionality)
• This change requires a documentation update
• This change requires execution against OCP (use run tests phrase in comment)

Checklist:

• Methods and classes used in PR scenarios are meaningful
• Commits are well encapsulated and follow the best practices

[michalvavrik]

@rsvoboda I am working on OpenShift, MsSQL adjustments suggested by Zheng and considering DEV mode (no effort yet). It call can be done in a separate PR as this one is already big. Thanks

[rsvoboda]

LGTM, it's quite complex topic and I would need quite some time to get more detailed knowledge. I didn't spot anything that would be suspicious to me.

Just some notes to the topic: as this needs quite some coding, it's necessary to think about the recovery upfront and not in retrospective. Another aspect is that recovery can't be handled by "ops", needs active involvement of the developer (if things go south).