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.