Alleviate the connection leak caused by Seata Client throwing exceptions in CONNECTION_STRICTLY connection mode

[linghengqian]

Fixes #34418 .

Changes proposed in this pull request:

• Alleviate the connection leak caused by Seata Client throwing exceptions in CONNECTION_STRICTLY connection mode.
• This is basically a variation of Alleviate connection leaks caused by Seata Client throwing exceptions #34463 . More investigation is at org.apache.shardingsphere.driver.jdbc.core.connection.DriverDatabaseConnectionManager#createConnections leaks connection if replay throws exception #34418 (comment) and https://shardingsphere.apache.org/document/current/en/reference/sharding/execute/ .
• No issue has ever provided a reproducible unit test. Currently all relevant unit tests actively exploit the connection leak bug on Seata Client 2.2.0.

---

Before committing this PR, I'm sure that I have checked the following options:

• My code follows the code of conduct of this project.
• I have self-reviewed the commit code.
• I have (or in comment I request) added corresponding labels for the pull request.
• I have passed maven check locally : ./mvnw clean install -B -T1C -Dmaven.javadoc.skip -Dmaven.jacoco.skip -e.
• I have made corresponding changes to the documentation.
• I have added corresponding unit tests for my changes.
• I have updated the Release Notes of the current development version. For more details, see Update Release Note

[linghengqian]

• Closing the current PR since the unit tests correctly assert this error.