Add GraalVM Reachability Metadata and corresponding nativeTest for HiveServer2

[linghengqian]

For #29052.

Changes proposed in this pull request:

• Add GraalVM Reachability Metadata and corresponding nativeTest for Hive. The irrelevant content of the current PR has been split into the following PRs.
  • Fixes the connection of Remote HiveServer2 through HiveServer2 JDBC Driver #31573
  • Bump the minimum GraalVM CE version required to compile ShardingSphere's GraalVM Native Image artifacts to JDK22 #31630
• shardingsphere-parser-sql-hive module does not support CREATE, SET,TRUNCATE, DROP statements yet. This is marked with a TODO.
• To execute SQL like DELETE FROM t_address WHERE address_id=?, we always need to execute some Hive Session-level SQL in the current javax.sql.DataSource. However, since the SQL parsing of set key=value is not supported, these SQLs are currently located in test-native/sql/test-native-databases-hive.sql and are directly passed through to the actual Hive database for processing.
• The current PR is disturbed by part of the external issue.
  • For https://issues.apache.org/jira/browse/HIVE-28295 . The current PR is using Remote HiveServer2 in Docker instead of Embedded HiveServer2.
  • For https://issues.apache.org/jira/browse/HIVE-28317 and https://issues.apache.org/jira/browse/HIVE-5867 . The initFile parameter of HiveServer2 JDBC Driver must be an absolute path. Maybe new properties can be added on the Hive side.
  • For https://issues.apache.org/jira/browse/HIVE-28316 and https://issues.apache.org/jira/browse/HIVE-28322 . Locally, after executing Insert SQL, 10 rows of data in Hive Database can be queried normally. However, in Github Actions, after executing Insert SQL, only part of the data can be queried. I tend to think this is a transaction bug on the apache/hive 4.0.0 side, because this phenomenon can always be observed on a single hive database regardless of whether shardingsphere is used to shard multiple hive databases.
  • For https://issues.apache.org/jira/browse/hive-28308 . Because the unknown Commit on the Hive side, org.apache.hive:hive-jdbc:4.0.0 does not contain any compile scope dependence.
  • For [SPARK-33343][BUILD] Fix the build with sbt to copy hadoop-client-runtime.jar spark#30250 . The shaded class org.apache.hadoop.shaded.com.ctc.wstx.io.InputBootstrapper from org.apache.hadoop:hadoop-client-api should not be excluded internally within org.apache.hive:hive-service:4.0.0, which necessitates excluding its internal dependency on org.apache.hadoop:hadoop-client-api and manually adding org.apache.hadoop:hadoop-client-api:3.3.5.
  • It is currently not convenient to operate on the t_order and t_order_item tables because org.apache.hive.jdbc.HiveStatement does not implement java.sql.Statement#getGeneratedKeys().
  • For [QUESTION] Should we collect GraalVM Reachability Metadata for shaded packages? oracle/graalvm-reachability-metadata#377 and grpc-netty-shaded cannot be successfully compiled under GraalVM grpc/grpc-java#10601 . Since io.grpc:grpc-netty-shaded:1.58.0 in org.apache.hive:hive-service:4.0.0 shades Netty, this shaded package requires additional native-image.properties. If the HiveServer2 JDBC Driver can remove the use of grpc-netty-shaded, it will obviously make the current PR less difficult to understand.

---

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.