Uses GraalVM CE For JDK 22.0.2 in CI to prevent OutOfMemoryError

[linghengqian]

Fixes https://github.com/apache/shardingsphere/actions/runs/9453545898/job/26039164284 .

Changes proposed in this pull request:

• Bump the Docker Images involved in testcontainers-java, clickhouse-java and nativeTest under GraalVM Native Image.
• Uses GraalVM CE For JDK 22.0.2 in CI to prevent OutOfMemoryError. This mainly concerns Added a few OutOfMemoryError-related fixes. mentioned in https://www.graalvm.org/release-notes/JDK_22/. This PR was forked from Add GraalVM Reachability Metadata and corresponding nativeTest for Iceberg table in HiveServer2 #31526 .

Build resources:
 - 7.43GB of memory (47.6% of 15.61GB system memory, determined at start)
 - 4 thread(s) (100.0% of 4 available processor(s), determined at start)
[junit-platform-native] Running in 'test listener' mode using files matching pattern [junit-platform-unique-ids*] found in folder [/home/runner/work/shardingsphere/shardingsphere/test/native/target/test-ids] and its subfolders.
[2/8] Performing analysis...  [******]                                                                 (437.9s @ 6.39GB)
GC warning: 274.1s spent in 267 GCs during the last stage, taking up 60.51% of the time.
            Please ensure more than 10.38GB of memory is available for Native Image
            to reduce GC overhead and improve image build time.
   56,914 reachable types   (86.0% of   66,197 total)
  100,714 reachable fields  (56.2% of  179,282 total)
  318,421 reachable methods (59.2% of  537,732 total)
   17,338 types, 2,551 fields, and 14,274 methods registered for reflection
      146 types,   233 fields, and   199 methods registered for JNI access
        4 native libraries: dl, pthread, rt, z

Terminating due to java.lang.OutOfMemoryError: GC overhead limit exceeded
The Native Image build process ran out of memory.
Please make sure your build system has more memory available.

---

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.