fix: EXPOSED-754 Fix global rollback mark not set on unchecked exception in spring transaction

[zbqmgldjfh]

Description

Summary of the change:

• Added a property isRollback managed by TransactionScope in an individual transaction. : SpringTransactionManager
• Add more test : SpringTransactionRollbackTest

Detailed description:

• What: Global rollback mark not properly set on Unchecked Exception in Spring Transaction
  

• Why: The issue arises when a method with a transaction is called more than once in a nested manner.
  In this case, the results from the inner transactions are not being propagated to the outer one.
  However, in Spring, it is the default behavior to mark the entire transaction for rollback.
  Even if the exception is caught using a try-catch block, the rollback mark remains.

• How: Add a simple isRollback property for Tx

---

Type of Change

Please mark the relevant options with an "X":

• Bug fix
• New feature
• Documentation update

Updates/remove existing public API methods:

• Is breaking change

Affected databases:

• MariaDB
• Mysql5
• Mysql8
• Oracle
• Postgres
• SqlServer
• H2
• SQLite

Checklist

• Unit tests are in place
• The build is green (including the Detekt check)
• All public methods affected by my PR has up to date API docs
• Documentation for my change is up to date

---

Related Issues

https://youtrack.jetbrains.com/issue/EXPOSED-754/Global-Rollback-Mark-Not-Properly-Set-on-Unchecked-Exception-in-Spring-Transaction

[bog-walk]

Thanks for recognizing this issue, the thorough PR, and pushing a fix @zbqmgldjfh !

[zbqmgldjfh]

Thank you for reviewing and merging the PR @bog-walk !!