Support connecting to HiveServer2 through database connection pools other than HikariCP

[linghengqian]

For #29052.

Changes proposed in this pull request:

• Support connecting to HiveServer2 through database connection pools other than HikariCP. HiveServer2 JDBC Driver seems to deliberately bypass all the convenient ways to implement JDBC specification. There are simple public methods to use in https://github.com/apache/hive/blob/rel/release-4.0.1/jdbc/src/java/org/apache/hive/jdbc/HiveDriver.java and https://github.com/apache/hive/blob/rel/release-4.0.1/jdbc/src/java/org/apache/hive/jdbc/HiveConnection.java . What I am referring to is exactly org.apache.hive.jdbc.HiveConnection#getConnectedUrl(). This creates an easy access.
• 
• As a successor to #33377 , add description of shardingsphere agent docker image for 5.5.2.
• Supports configuring ShardingSphere under GraalVM Native Image to connect to HiveServer2 with ZooKeeper Service Discovery enabled.
• A very suspicious thing is that the shardingsphere jdbc datasource is not closed normally in the unit test, which leads to,
  1. The database started by testcontainers-java is not closed immediately. This only affects unit tests that use the testcontainers java style jdbcurl, and there are only 3 unit tests that use testcontainers like this.
  2. org.apache.shardingsphere.transaction.base.seata.at.SeataATShardingSphereTransactionManager#close() is never called normally. This leads to a large number of logs in https://github.com/apache/shardingsphere/actions/runs/11953880634/job/33322727601 due to the failure of seata client to close normally.

     Error:  2024-11-21 13:26:47.684 [timeoutChecker_2_1] o.a.s.c.r.n.NettyClientChannelManager - connect server failed. can not connect to [127.0.0.1:32771]
     org.apache.seata.common.exception.FrameworkException: can not connect to [127.0.0.1:32771]
     at org.apache.seata.core.rpc.netty.NettyClientChannelManager.doReconnect(NettyClientChannelManager.java:251)
     at org.apache.seata.core.rpc.netty.NettyClientChannelManager.doReconnect(NettyClientChannelManager.java:212)
     at org.apache.seata.core.rpc.netty.NettyClientChannelManager.reconnect(NettyClientChannelManager.java:167)
     at org.apache.seata.core.rpc.netty.AbstractNettyRemotingClient.lambda$init$0(AbstractNettyRemotingClient.java:109)
     at java.base@22.0.2/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:572)
     at java.base@22.0.2/java.util.concurrent.FutureTask.runAndReset(FutureTask.java:358)
     at java.base@22.0.2/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305)
     at java.base@22.0.2/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144)
     at java.base@22.0.2/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642)
     at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
     at java.base@22.0.2/java.lang.Thread.runWith(Thread.java:1583)
     at java.base@22.0.2/java.lang.Thread.run(Thread.java:1570)
     at org.graalvm.nativeimage.builder/com.oracle.svm.core.thread.PlatformThreads.threadStartRoutine(PlatformThreads.java:853)
     at org.graalvm.nativeimage.builder/com.oracle.svm.core.thread.PlatformThreads.threadStartRoutine(PlatformThreads.java:829)

---

Before committing this PR, I'm sure that I have checked the following options:

• [x] My code follows the code of conduct of this project.
• [x] I have self-reviewed the commit code.
• [x] I have (or in comment I request) added corresponding labels for the pull request.
• [x] I have passed maven check locally : ./mvnw clean install -B -T1C -Dmaven.javadoc.skip -Dmaven.jacoco.skip -e.
• [x] I have made corresponding changes to the documentation.
• [x] I have added corresponding unit tests for my changes.
• [x] I have updated the Release Notes of the current development version. For more details, see Update Release Note