[Fix][Core] Introduce SeaTunnel CompletableFuture to prevent ForkJoinPool thread shortage

[Hisoka-X]

Purpose of this pull request

In Zeta and Connector, we extensively use Java's CompletableFuture object, and there are cases where CompletableFuture tasks are nested. The default ForkJoinPool thread pool is insufficient under heavy load. To address this, we introduced our own CompletableFuture in Zeta, leveraging a cached thread pool for task execution. Additionally, we modified Hazelcast's internal InvocationFuture to use the same thread pool.

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 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
• Update the release-note.

[hailin0]

Suggested change

	r, "CompletableFuture-Thread-" + seq.getAndIncrement());
	r, "SeaTunnel-CompletableFuture-Thread-" + seq.getAndIncrement());