FINERACT-2525: Accept MariaDB snapshot isolation conflict responses in savings integration tests

[udayagiri-sivasai-dev]

What changed

• Updated SavingsAccountTransactionTest to accept MariaDB 12.2 snapshot-isolation conflict responses that return 403 with "Record has changed since last read".

Why

• Under MariaDB 12.2 with innodb_snapshot_isolation=ON, concurrency tests can return a different valid conflict response than the tests previously allowed.

How I tested

• :integration-tests:test --tests "*SavingsAccountTransactionTest.testDeadlockSavingsBatchTransactions"
• :integration-tests:test --tests "*SavingsAccountTransactionTest.testConcurrentSavingsBatchTransactions"
• :integration-tests:test --tests "*SavingsAccountTransactionTest"

[San-43]

Please sign your commits as described in the CONTRIBUTING.md signing guide.

[oleksii-novikov-onix]

Matching on Record has changed since last read is fragile - if database changes the error message text in a future version, these tests will break again. If the exception were classified as SomeConcurrencyException(not sure, need to check what the actual exception being thrown is) at the ErrorHandler level instead, it would map to 409, and the tests would just work since they already accept SC_CONFLICT.

[udayagiri-sivasai-dev]

Updated this based on your suggestion.

Instead of matching that message in the test, I changed the exception classification in ErrorHandler so the MariaDB snapshot-isolation case (Record has changed since last read) is treated as a concurrency / pessimistic locking failure and follows the existing 409 Conflict path.

I also verified it locally with:

• SavingsAccountTransactionTest.testDeadlockSavingsBatchTransactions
• SavingsAccountTransactionTest.testConcurrentSavingsBatchTransactions

[adamsaghy]

gradle/actions: Writing build results to /home/runner/work/_temp/.gradle-actions/build-results/__run-1776850844187.json
FAILURE: Build failed with an exception.


[Incubating] Problems report is available at: file:///home/runner/work/fineract/fineract/build/reports/problems/problems-report.html
* What went wrong:

Execution failed for task ':fineract-core:checkstyleMain'.
Deprecated Gradle features were used in this build, making it incompatible with Gradle 9.0.
> A failure occurred while executing org.gradle.api.plugins.quality.internal.CheckstyleAction

   > Checkstyle rule violations were found. See the report at: file:///home/runner/work/fineract/fineract/fineract-core/build/reports/checkstyle/main.html
You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.
     Checkstyle files with violations: 1

     Checkstyle violations by severity: [error:1]

Please run:
./gradlew spotlessApply spotbugsMain spotbugsTest checkstyleMain checkstyleTest
./gradlew --no-daemon build -x test -x cucumber -x doc

Before any PR or changes, please always run these two commands and make sure there is green build!