Open the resource:/ related FileSystem for JDBCRepositorySQLLoader in the GraalVM Native Image environment

[linghengqian]

For #29000.

Changes proposed in this pull request:

• Open the resource:/ related FileSystem for JDBCRepositorySQLLoader in the GraalVM Native Image environment.
• Also for Make ShardingSphere Proxy in GraalVM Native Image form available #21347.
• Under the GraalVM Native Image corresponding to GraalVM CE 21.0.1, although there is NativeImageResourceFileSystemProvider , the corresponding NativeImageResourceFileSystem does not autoload. This is mainly to align the behavior of ZipFileSystemProvider, so we need to manually open and close the FileSystem corresponding to the resource:/ scheme. For more background reference Cannot open native image resource using Path, NativeImageResourceFileSystemProvider not initialised oracle/graal#7682 .
• we use the System Property of org.graalvm.nativeimage.imagecode to identify whether this class is in the GraalVM Native Image environment. The background of this property comes from Annotation Interface DisabledInNativeImage on Junit.

---

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]

• Naturally, we can continue to keep similar operations within specific unit tests, because the current behavior is actually consistent with the behavior in Jar. Calling resource URI inside Jar also requires opening FileSystem. I'm still looking for a review.