[Fix][Connector-V2] Ignore JdbcConnectorException on JDBC statement close

[dybyte]

Fixes: #9886

Purpose of this pull request

This PR ignores JdbcConnectorException thrown during remaining batch execution in closeStatements() and logs the error instead of propagating the exception.
When executeBatch() is called in closeStatements(), a JdbcConnectorException may occur if the statement is already closed. Ignoring this exception is preferable, as propagating it can cause confusion in upper layers.
For more details, please refer to the related issue.

Does this PR introduce any user-facing change?

No.

How was this patch tested?

No additional tests were added for this change.

Check list

• If any new Jar binary package adding in your PR, please add License Notice according
  New License Guide
• If necessary, please update the documentation to describe the new feature. https://github.com/apache/seatunnel/tree/dev/docs
• If you are contributing the connector code, please check that the following files are updated:
  1. Update plugin-mapping.properties and add new connector information in it
  2. Update the pom file of seatunnel-dist
  3. Add ci label in label-scope-conf
  4. Add e2e testcase in seatunnel-e2e
  5. Update connector plugin_config

[Carl-Zhou-CN]

LGTM

[dybyte]

Hi @davidzollo, PTAL when you have a moment. Thanks!