Add documentation for P6Spy support

[linghengqian]

Ref #29052.

Changes proposed in this pull request:

• Add documentation for P6Spy support. For add p6spy driver support to ShardingJDBC infra #31814 . One important point to note here is that the P6Spy SPI implementation was actually only added for MySQL.
• Fixes https://github.com/apache/shardingsphere/actions/runs/12316270364/job/34376201179 . Fix NativeTest failure due to class changes.
• Bump GraalVM Native Build Tools to 0.10.4 . This is mainly influenced by Make accessFilter file registration thread safe graalvm/native-build-tools#635 .
• Replace the OpenGauss Docker Image of nativeTest under GraalVM Native Image from opengauss/opengauss:5.0.0 to enmotech/opengauss-lite:5.1.0. Although opengauss/opengauss is still confirmed as the official Docker Image of OpenGauss in places such as https://opengauss.org/zh/news/2023-03-10/ , it is no longer updated. Articles like https://opengauss.org/zh/blogs/zhengwen2/openGauss%E5%BF%AB%E9%80%9F%E5%AE%89%E8%A3%85%E6%96%B9%E6%B3%95(docker).html indicate that the OpenGauss community prefers the Docker Images of enmotech/opengauss and enmotech/opengauss-lite. Due to issues like Provides Docker Image of OpenGauss 6.0.0 for enmotech/opengauss-lite enmotech/enmotech-docker-opengauss#52 , enmotech/opengauss cannot be used in WSL or Dev Container. Using enmotech/opengauss-lite is a more reasonable choice.
• Remove dependency on org.testcontainers:clickhouse until [Enhancement]: org.testcontainers.containers.ClickHouseProvider should use clickhouse/clickhouse-server as Docker Image testcontainers/testcontainers-java#8736 is resolved.

---

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