S3 test suites can no longer pull the minio/minio image #6884

Describe the bug

CometS3TestBase starts MinIO from minio/minio:latest, and Docker Hub now refuses that pull:

Status 404: {"message":"pull access denied for minio/minio, repository does not exist or may require 'docker login': denied: requested access to the resource is denied"}

quay.io/minio/minio is refused as well. So every suite that mixes in CometS3TestBase (ParquetReadFromS3Suite, IcebergReadFromS3Suite, CometS3CredentialBridgeSuite, HadoopS3ACredentialProviderAdapterBridgeSuite) fails in beforeAll before any test runs. The PR workflows don't list these suites, which is why CI on main stays green.

Found in #5365, where the Delta S3 job builds on CometS3TestBase and failed on the pull: https://github.com/apache/datafusion-comet/actions/runs/38233957666/job/114789734253

Steps to reproduce

docker pull minio/minio:latest
./mvnw test -Dtest=none -Dsuites=org.apache.comet.parquet.ParquetReadFromS3Suite

Expected behavior

The S3 suites start a MinIO container and run.

Additional context

cgr.dev/chainguard/minio is still published. Declaring it with asCompatibleSubstituteFor("minio/minio") lets MinIOContainer accept it, and #5365's Delta S3 suite passed against it locally.

Willingness to contribute

I can contribute a fix for this bug independently