Add GraalVM Reachability Metadata and corresponding nativeTest for Presto Memory Connector

[linghengqian]

For #29052.

Changes proposed in this pull request:

• Add GraalVM Reachability Metadata and corresponding nativeTest for Presto Memory Connector.
• Prestissimo is not the focus of this PR because this PR only focuses on the processing of the Presto JDBC Driver side.
• Parts not relevant to this PR will be split,
  • Support for connecting to Presto's Memory Connector in ShardingSphere config #34432
  • Missing an HTTP endpoint to ensure the Presto Docker Container is ready prestodb/presto#23226
  • Alleviate connection leaks caused by Seata Client throwing exceptions #34463
  • The log output of org.graalvm.buildtools.maven.MetadataCopyMojo has Typo graalvm/native-build-tools#689

---

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]

• Presto Server's healthcheck started to behave strangely. After executing SQL statements such as CREATE SCHEMA memory.demo_ds_0, the return value of /v1/info/state on the 8080 port of Presto Server would switch from "ACTIVE" to other values ​​within an unknown period of time. This ultimately results in the error log No nodes available to run query being displayed.

[linghengqian]

• Bypassing prestodb/presto#23226 is not a good thing. This introduces unstable CI.

[linghengqian]

• An interesting turn of events occurred in presto 0.292 compared to presto 0.290. See #35504 .