Split nativeTest modules for JDBC and Proxy

[linghengqian]

For #29052.

Changes proposed in this pull request:

• Split nativeTest modules for JDBC and Proxy. The current PR was split from Add GraalVM Reachability Metadata and corresponding nativeTest for Firebird #34307 to facilitate review.
• Executing org.apache.shardingsphere.test.natived.proxy.transactions.base.SeataTest will break Firebird unit tests in CI environment. This only happens under GraalVM Native Image. In order to investigate what exactly is the missing GraalVM reachability metadata JSON, it is necessary to raise the current PR.
• More background at https://www.yuque.com/linghengqian/meve2v/es8d3a8a18odao7x and [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 . Previously, the GRM JSON related to org.apache.shardingsphere.mode.repository.standalone.jdbc.sql.JDBCRepositorySQL only worked when the SS Proxy class was in the GraalVM Native Image. This was apparently because the judgment condition was not complete. Isolating the unit tests for JDBC and Proxy into different Maven modules is enough to handle this issue from a classpath perspective. Because the processing principle of GraalVM Tracing Agent is either based on classpath or module.

{
  "condition":{"typeReachable":"org.apache.shardingsphere.proxy.initializer.BootstrapInitializer"},
  "name":"org.apache.shardingsphere.mode.repository.standalone.jdbc.sql.JDBCRepositorySQL",
  "allDeclaredFields":true,
  "queryAllDeclaredMethods":true,
  "queryAllDeclaredConstructors":true
}

---

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]

My understanding is that there is absolutely no way I can work on the current issue until graalvm/native-build-tools#650 is resolved.