Add transaction-API scenario / Classic flavor

[pjgg]

Summary

Jira Ref: https://issues.redhat.com/browse/QUARKUS-2492

Add Quarkus transaction programmatic API scenario / Classic flavor

• Programmatic API transaction
• Lambda API transaction
• Rollback

Covered databases: Oracle, Mysql, Mssql, MariaDB and postresql
SmokeTest over: openAPI, tracing and metrics

Please select the relevant options.

• 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

[pjgg]

run tests

[fedinskiy]

And one more thing: it was missed during test plans phase, but could you consider adding our "full picture" topics (logging/tracing/metrics/security and openapi)? I presume, that at least metrics and security can be of interest in that case.

[pjgg]

And one more thing: it was missed during test plans phase, but could you consider adding our "full picture" topics (logging/tracing/metrics/security and openapi)? I presume, that at least metrics and security can be of interest in that case.

There are no integration surfaces between narayana+security, narayana+micrometer or narayana+openAPI
that security is handled either by persistence or endpoints and there are absolutely no metrics provided by narayana extension, that all the gauges have to be manual.

[pjgg]

run tests

[pjgg]

OCP IT test:
JVM mode: Quarkus QE TS: SQL Database: Narayana-transactions . SUCCESS [06:33 min]
Native Mode: [INFO] Quarkus QE TS: SQL Database: Narayana-transactions . SUCCESS [24:44 min]

[fedinskiy]

CI failures are not in database modules and therefore, probably, unrelated