Prevent use of GraalVM Native Build Tools Maven Plugin in parallel builds of project

[linghengqian]

For #29052.

Changes proposed in this pull request:

• Prevent use of GraalVM Native Build Tools Maven Plugin in parallel builds of project. This is one of the findings from Unable to build nativeTest under GraalVM Native Image in parallel linghengqian/hive-server2-jdbc-driver#3. The Maven Plugin of GraalVM Native Build Tools is not thread-safe, and using the features of https://cwiki.apache.org/confluence/display/MAVEN/Parallel+builds+in+Maven+3 will cause problems. But it is hard to say that I know how to implement parallel construction of GraalVM Native Image on the GraalVM Native Build Tools side. The Native Image constructor uses up 3/4 of the system's maximum memory by default.
• Fixes https://github.com/apache/shardingsphere/actions/runs/10424218529/job/28872589371 . Temporarily blocked org.apache.shardingsphere.infra.expr.espresso.EspressoInlineExpressionParserTest from running on OpenJDK 22, mainly because the performance of Github Actions instrumentation was too low, and launching nested JVMs within JVMs often caused CI timeouts. The current PR restricts the relevant unit tests to run only under GraalVM CE. In fact, it can also run under local OpenJDK 21-24.
• Bump Groovy to 4.0.22. This is useful for syntax testing in the Groovy Web Console. Reference https://groovyconsole.dev/ .
• Bump testcontainers-java to 1.20.1. Carry Fix log order after checking containerised compose exit code testcontainers/testcontainers-java#8984 to optimize the out-of-order log of testcontainers-java.
• Bump third-party builds of HiveServer2 JDBC Driver. Mainly to sync POM constraints on apache/hive 4.0.0.
• Provides source information for the documentation of Iceberg tables for HiveServer2 JDBC Driver. As a statement, it is mainly Cloudera that is driving the Apache Iceberg table format to replace the traditional Hive table format, not others.
• Set native-image-job-reports to true and prevent sharing the cache with other jobs. This helps to get rid of the tens of thousands of lines of CI Log to view the performance information of nativeTest. An example from https://github.com/apache/shardingsphere/actions/runs/10438004530?pr=32574 .
• 

---

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.