Prevent ReadwriteSplitting rule class from parsing Groovy syntax under GraalVM Native Image

[linghengqian]

For #21347.

Changes proposed in this pull request:

• Prevent ReadwriteSplitting rule class from parsing Groovy syntax under GraalVM Native Image. According to Make ShardingSphere Proxy in GraalVM Native Image form available #21347, we need to block calls to GroovyShell related classes under GraalVM Native Image.
• This PR brings out a magical hidden feature. In ReadwriteSplitting, <data_source_name>, <data_source_name>.write_data_source_name and <data_source_name>.read_data_source_names are allowed to be configured through Groovy Expressions. No matter in the Example module, the unit tests do not reflect this, and the documentation does not mention it. It looks like the relevant unit test was removed in a past commit.
• Also for Provides built-in GraalVM Reachability Metadata for core features of ShardingSphere JDBC and adds nativeTest-related unit test subsets #29000 .

---

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.

[linghengqian]

• I realize this PR is completely pointless. I'd be inclined to open a PR to supplement the documentation to request that the downstream switch use another implementation of the Row Value Expression SPI, which would also solve nativetest in GraalVM Native Image.