Refactor NativeTest to prevent failures in building GraalVM Native Image

[linghengqian]

For #29052 .

Changes proposed in this pull request:

• Refactor NativeTest to prevent failures in building GraalVM Native Image. See [GR-60457] [GR-52400] Revise heuristic for memory usage of Native Image build process. oracle/graal#10441 on GraalVM CE For JDK 25 milestone. GraalVM CE For JDK 24.0.2 always likes to limit the used memory to a smaller size when the CI system memory is small. GraalVM has some fancy code logic to determine if it is running in a CI environment. For more information, see the findings at Prevent generateMetadata Profiles from generating GraalVM Reachability Metadata for arrays and JdkLogger #36067 (comment) .
• Bump the Linux Container used by the NativeTest test suite.
  • clickhouse/clickhouse-server:25.6.5.41
  • mcr.microsoft.com/mssql/server:2022-CU20-ubuntu-22.04
  • firebirdsql/firebird:5.0.3
  • mysql:9.4.0-oraclelinux9
  • postgres:17.5-bookworm
• Bump unit test libraries of junit-framework, testcontainers-java, awaitility. See Add missing JUnit 5.13.0 types to initialize-at-build-time classes graalvm/native-build-tools#728 .
• Update ClickHouse integration documentation to reflect incompatibility reporting for ClickHouse JDBC Driver V2, and use of environment variable CLICKHOUSE_SKIP_USER_SETUP.
• Update HiveServer2 integration documentation to reflect changes in fix:Support Hive TRUNCATE TABLE statement parse #36049, fix:Support Hive CREATE TABLE statement parse #36040, fix:Support Hive DROP TABLE statement parse #36018 .

---

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