[java-shared-config] Address coverage gap in GraalVM for FileSystemProviders

Releasing https://github.com/googleapis/java-shared-config/pull/854 which migrates from using graalvm jdk 11 ce images to graalvm for jdk 17 community image caused tests in java-storage-nio to fail (See https://github.com/googleapis/java-storage-nio/issues/1447).

Options:

- Add java-storage-nio tests to GraalVM cloudbuild jobs.
- [More lightweight] Introduce canary test to native image compilation with FileSystemProvider. The use of this class causes some classes to be initializes at build time during native image compilation. This has also resulted in varying behavior based on which GraalVM for JDK version is used. https://github.com/oracle/graal/issues/5134 is one known issue where the recommended `-H:-AddAllFileSystemProviders` parameter works in JDK 21 to address the build-time failures related to FileSystemProviders but continues to fail in JDK 17.