Add GraalVM Reachability Metadata and corresponding nativeTest for Firebird

[linghengqian]

For #29052.

Changes proposed in this pull request:

• Add GraalVM Reachability Metadata and corresponding nativeTest for Firebird.
• Non-essential parts of this PR have been split into other PRs, including,
  • Fix the Flaky Test related to ClickHouse in NativeTest under GraalVM Native Image #34333
  • Support connecting to Firebird via jdbcUrl containing the absolute path to fdb #34335
  • Split nativeTest modules for JDBC and Proxy #34358
• The current PR is affected by multiple external issues.
  • According to https://firebirdsql.org/en/news/official-firebird-docker-images , there is no official Docker Image for Firebird. Use the recommended /~https://github.com/fdcastel/firebird-docker instead
  • Cannot use create table if not exists for Docker Image ghcr.io/fdcastel/firebird:5.0.1, see Create if not exists FirebirdSQL/firebird#8062
  • Docker Image ghcr.io/fdcastel/firebird:5.0.1 does not work with DROP TABLE IF EXISTS, see DROP [IF EXISTS] ... [CORE3863] FirebirdSQL/firebird#4203
  • Docker Image ghcr.io/fdcastel/firebird:5.0.1 cannot use TRUNCATE TABLE, see Add TRUNCATE TABLE [CORE2479] FirebirdSQL/firebird#2892
  • Due to Support executing CREATE DATABASE statements [JDBC598] FirebirdSQL/jaybird#629 and /~https://github.com/FirebirdSQL/jaybird/blob/master/devdoc/jdp/jdp-2024-02-create-database-through-jdbc-url.adoc , the SQL statement Create Database cannot be executed on the Firebird JDBC driver. Unit testing requires the use of org.firebirdsql.management.FBManager.
• Temporarily disable unit testing of Seata integration of Proxy Native. It's strange that starting Seata Client causes connection leak in Firebird's NativeTest. This requires a separate investigation.

---

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

[linghengqian]

• The interesting thing is that I cannot reproduce the error log of /~https://github.com/apache/shardingsphere/actions/runs/12734368802/job/35491847525?pr=34307 locally.

Failures (1):
  JUnit Jupiter:FirebirdTest:assertShardingInLocalTransactions()
    MethodSource [className = 'org.apache.shardingsphere.test.natived.jdbc.databases.FirebirdTest', methodName = 'assertShardingInLocalTransactions', methodParameterTypes = '']
    => java.sql.SQLTransientConnectionException: HikariPool-65 - Connection is not available, request timed out after 30000ms.
       com.zaxxer.hikari.pool.HikariPool.createTimeoutException(HikariPool.java:696)
       com.zaxxer.hikari.pool.HikariPool.getConnection(HikariPool.java:197)
       com.zaxxer.hikari.pool.HikariPool.getConnection(HikariPool.java:162)
       com.zaxxer.hikari.HikariDataSource.getConnection(HikariDataSource.java:128)
       org.apache.shardingsphere.driver.jdbc.core.connection.DriverDatabaseConnectionManager.createConnection(DriverDatabaseConnectionManager.java:375)

• 
• 
• Maybe there is something I'm not aware of and the connection leak only happens in the Github Actions device.
• update in 2025.01.12: According to the results of /~https://github.com/apache/shardingsphere/actions/runs/12734759305/job/35492699852?pr=34307 , org.apache.shardingsphere.test.natived.jdbc.databases.FirebirdTest runs fine under normal JVM, but fails under GraalVM Native Image, which is interesting.
• update in 2025.01.14: According to the test results of /~https://github.com/apache/shardingsphere/actions/runs/12768181816/job/35588020566?pr=34307 , org.apache.shardingsphere.test.natived.proxy.transactions.base.SeataTest's NativeTest will cause connection leaks and destroy the unit test of SS JDBC, which is too outrageous.
• update in 2025.01.15: First, we need to deal with Split nativeTest modules for JDBC and Proxy #34358 . Otherwise, I won’t know what the missing GraalVM Reachability Meatdata is, and the log will be too messy.
• update in 2025.01.18: My understanding is that there is absolutely no way I can work on the current issue until [ERROR] Metadata copy process failed with code: 1 is thrown when using native:metadata-copy in a multi-module Maven project graalvm/native-build-tools#650 is resolved.
• update in 2025.01.19: Seata's RM Client's behavior after destruction is very suspicious. I need to confirm something else.

[INFO] Running org.apache.shardingsphere.test.natived.jdbc.transactions.base.SeataTest
[ERROR] 2025-01-19 11:44:05.205 [main] o.a.s.config.ConfigurationFactory - failed to load non-spring configuration :not found service provider for : org.apache.seata.config.ConfigurationProvider
org.apache.seata.common.loader.EnhancedServiceNotFoundException: not found service provider for : org.apache.seata.config.ConfigurationProvider
[ERROR] 2025-01-19 11:44:05.427 [AsyncWorker_1_1_2] o.a.seata.rm.datasource.AsyncWorker - Failed to batch delete undo log
org.postgresql.util.PSQLException: An I/O error occurred while sending to the backend.
        at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:398)
        at org.postgresql.jdbc.PgStatement.executeInternal(PgStatement.java:502)
        at org.postgresql.jdbc.PgStatement.execute(PgStatement.java:419)
        at org.postgresql.jdbc.PgPreparedStatement.executeWithFlags(PgPreparedStatement.java:194)
        at org.postgresql.jdbc.PgPreparedStatement.executeUpdate(PgPreparedStatement.java:155)
        at com.zaxxer.hikari.pool.ProxyPreparedStatement.executeUpdate(ProxyPreparedStatement.java:61)
        at com.zaxxer.hikari.pool.HikariProxyPreparedStatement.executeUpdate(HikariProxyPreparedStatement.java)
        at org.apache.seata.rm.datasource.undo.AbstractUndoLogManager.batchDeleteUndoLog(AbstractUndoLogManager.java:179)
        at org.apache.seata.rm.datasource.AsyncWorker.deleteUndoLog(AsyncWorker.java:182)
        at org.apache.seata.rm.datasource.AsyncWorker.dealWithGroupedContexts(AsyncWorker.java:162)
        at java.base/java.util.HashMap.forEach(HashMap.java:1429)
        at org.apache.seata.rm.datasource.AsyncWorker.doBranchCommit(AsyncWorker.java:125)
        at org.apache.seata.rm.datasource.AsyncWorker.doBranchCommitSafely(AsyncWorker.java:107)
        at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:572)
        at java.base/java.util.concurrent.FutureTask.runAndReset(FutureTask.java:358)
        at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305)
        at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144)
        at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642)
        at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
        at java.base/java.lang.Thread.run(Thread.java:1570)
Caused by: java.io.EOFException: null
        at org.postgresql.core.PGStream.receiveChar(PGStream.java:469)
        at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:2166)
        at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:371)
        ... 19 common frames omitted
[ERROR] 2025-01-19 11:44:05.428 [AsyncWorker_1_1_2] o.a.seata.rm.datasource.AsyncWorker - Failed to rollback JDBC resource after deleting undo log failed
java.sql.SQLException: Connection is closed
        at com.zaxxer.hikari.pool.ProxyConnection$ClosedConnection.lambda$getClosedConnection$0(ProxyConnection.java:515)
        at jdk.proxy3/jdk.proxy3.$Proxy37.rollback(Unknown Source)
        at com.zaxxer.hikari.pool.ProxyConnection.rollback(ProxyConnection.java:396)
        at com.zaxxer.hikari.pool.HikariProxyConnection.rollback(HikariProxyConnection.java)
        at org.apache.seata.rm.datasource.AsyncWorker.deleteUndoLog(AsyncWorker.java:189)
        at org.apache.seata.rm.datasource.AsyncWorker.dealWithGroupedContexts(AsyncWorker.java:162)
        at java.base/java.util.HashMap.forEach(HashMap.java:1429)
        at org.apache.seata.rm.datasource.AsyncWorker.doBranchCommit(AsyncWorker.java:125)
        at org.apache.seata.rm.datasource.AsyncWorker.doBranchCommitSafely(AsyncWorker.java:107)
        at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:572)
        at java.base/java.util.concurrent.FutureTask.runAndReset(FutureTask.java:358)
        at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305)
        at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144)
        at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642)
        at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
        at java.base/java.lang.Thread.run(Thread.java:1570)
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 37.43 s -- in org.apache.shardingsphere.test.natived.jdbc.transactions.base.SeataTest