Log and fix interrupted transactions

[wezell]

We have wrapped almost all of our modern APIs and Factories (those that expect to write to the DB) in our @WrapTransaction annotation. This has been great, as this has proven to provide transactional control at a method level. One issue we have seen is that many API calls that are intended to be transactional actually call other older APIs or legacy code that do not respect any transactions and these older apis can commit and closes connections unexpectedly in what should be an ongoing transaction.

This behavior has been going on since time began at dotCMS and has not had any obvious damaging effects as another DB connection just takes the originals place. But obviously, these unwanted commits are bad behavior and could possibly underlie a number of hard to pin down or unreproducible failures, such as can happen when publishing large bundles.

At the very least, we should log these unwanted transaction commits and fix them when we see them.

[wezell]

Out of the box, it will only log the error, but I think for tests we would want to throw an exception so we can find places in code where this happens. You can do this by setting
LOCAL_TRANSACTION_INTERUPTED_ACTION=THROW. If you want to turn off all error logging, just omit the property or set it to
LOCAL_TRANSACTION_INTERUPTED_ACTION=NOTHING

[jgambarios]

PR: #16830