[GH-3355] Pull the MinIO test image from quay.io

[jiayuasu]

Did you read the Contributor Guide?

• Yes, I have read the Contributor Rules and Contributor Development Guide

Is this PR related to a ticket?

• Yes, and the PR name follows the format [GH-XXX] my subject. Closes CI: MinIO-backed tests fail because Docker Hub no longer serves minio/minio #3355

What changes were proposed in this PR?

Docker Hub no longer serves the minio/minio repository, so every Testcontainers-based MinIO test fails to start and, with fail-fast, takes the whole Scala and Java build matrix down. This switches the four call sites (OsmReaderTest and the three GeoPackageReaderTest copies) to the same image on quay.io, pinned to a release tag instead of latest:

new MinIOContainer(
  DockerImageName
    .parse("quay.io/minio/minio:RELEASE.2025-09-07T16-13-09Z")
    .asCompatibleSubstituteFor("minio/minio"))

asCompatibleSubstituteFor is required because MinIOContainer asserts that the image is compatible with minio/minio. RELEASE.2025-09-07T16-13-09Z is the build quay's latest tag points at today, so this is the image the tests were already using.

How was this patch tested?

• Test sources of spark/common and spark/spark-3.5 compile with the change.
• The container tests need Docker, which is not available on my machine, so the real verification is this PR's CI run: the previously failing OsmReaderTest and GeoPackageReaderTest S3 cases should now start their MinIO container and pass.

Did this PR include necessary documentation updates?

• No, this PR does not affect any public API so no need to change the documentation.