[Fix] Fix log error when multi-table sink close

[Hisoka-X]

Purpose of this pull request

Fix MultiTableSinkWriter will log error even job execute successed. This cause by MultiTableWriterRunnable, it will reported InterruptedException sometimes when be closed by ExecutorService. So this PR ignore this Exception when task close. This exception will be like:

2023-10-21 11:48:32,838 ERROR org.apache.seatunnel.connectors.seatunnel.common.multitablesink.MultiTableWriterRunnable - MultiTableWriterRunnable error
java.lang.InterruptedException: null
        at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.reportInterruptAfterWait(AbstractQueuedSynchronizer.java:2019) ~[?:1.8.0_362]
        at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2093) ~[?:1.8.0_362]
        at java.util.concurrent.LinkedBlockingQueue.poll(LinkedBlockingQueue.java:467) ~[?:1.8.0_362]
        at org.apache.seatunnel.connectors.sea2023-10-21 11:48:32,838 INFO  org.apache.seatunnel.engine.server.TaskExecutionService - [localhost]:5801 [seatunnel-597158] [5.1] Task TaskGroupLocation{jobId=767957395316932609, pipelineId=1, taskGroupId=50000} complete with state FINISHED
tunnel.common.multitablesink.MultiTableWriterRunnable.run(MultiTableWriterRunnable.java:47) [connector-fake-2.3.4-SNAPSHOT.jar:2.3.4-SNAPSHOT]
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:1.8.0_362]
        at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:1.8.0_362]
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0_362]
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0_362]
        at java.lang.Thread.run(Thread.java:750) [?:1.8.0_362]
2023-10-21 11:48:32,853 INFO  org.apache.seatunnel.engine.server.CoordinatorService - [localhost]:5801 [seatunnel-597158] [5.1] Received task end from execution TaskGroupLocation{jobId=767957395316932609, pipelineId=1, taskGroupId=50000}, state FINISHED

This bug does not affect the correctness of the job, it just prints confusing error logs in the log.

Does this PR introduce any user-facing change?

no

How was this patch tested?

add new test.

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 change log that in connector document. For more details you can refer to connector-v2
  2. Update plugin-mapping.properties and add new connector information in it
  3. Update the pom file of seatunnel-dist
• Update the release-note.

[ruanwenjun]

LGTM

[hailin0]

LGTM