Bump the minimum Seata Client version for Seata integration to 2.1.0 to serve nativeTest under GraalVM Native Image

[linghengqian]

For #29052.

Changes proposed in this pull request:

• Bump the minimum Seata Client version for Seata integration to 2.1.0 to serve nativeTest under GraalVM Native Image. This unifies the experience under HotSpot VM and GraalVM Native Image. Let everyone forget about Seata Client 1.x.
• Affected by Provide built-in GraalVM Reachability Metadata on Seata Client 2.1.0+ incubator-seata#6686, we need to maintain the GraalVM Reachability Metadata of seata client on shardingsphere side.
• Due to org.apache.seata:seata-mock-server depends on the non-existent org.apache.seata:seata-server incubator-seata#6882, org.apache.seata.mockserver.MockServer cannot be used.
• CI's logs are being polluted by Seata Client, I've opened When using Seata Client 2.1.0, an error message is not found service provider for: org.apache.seata.config.ConfigurationProvider incubator-seata#6886 . See https://github.com/apache/shardingsphere/actions/runs/11081012275/job/30792243532?pr=33030 .

Error:  2024-09-28 04:35:08.084 [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

• Since Seata started to use stricter server-side validation to handle global distributed transactions, the JDBC URL of jdbc:mock://127.0.0.1/foo_ds used by org.apache.shardingsphere.test.fixture.jdbc.MockedDataSource is no longer valid. We need to directly simulate the database supported by Seata AT mode such as MySQL, and update the handling of SeataATShardingSphereTransactionManager#commit(boolean). The document has been updated.
• Although OracleLabs claims that com.oracle.database.jdbc:ojdbc8 is production-ready under GraalVM Native Image at https://www.graalvm.org/native-image/libraries-and-frameworks/, according to Fatal error when running nativeTest with ojdbc 23.3.0.23.09 oracle/graal#7979, com.oracle.database.jdbc:ojdbc8 will cause CI to fail sporadically on any device. I simply cannot accept writing nativeTests for Oracle JDBC Driver while the issue is still open. As a clarification, the documentation has been updated.
• As a clarification to connection disabled when use com.alibaba.druid.pool.DruidDataSource #32765 (comment) , the documentation for HiveServer2 JDBC Driver has been updated.

---

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.

[strongduanmu]

Good job, merged.