Hello, We have MinIO support as S3 compatible storage and this is great as it allows users to quickly test out Apache Polaris as a catalog and write to a S3 compatible storage. However, as MinIO is now under maintenance mode only for OSS (https://github.com/minio/minio?tab=readme-ov-file), we won't be able to get updated images from public image registry, should we consider switch our primary getting-start example to non-MinIO one instead (the current one is MinIO as backend: https://github.com/apache/polaris/blob/main/getting-started/quickstart/docker-compose.yml)? Without doing so, users will be likely pulling down outdated MinIO images with critical CVEs couple months later for their local setup to play around. If using outdated MinIO is a concern as the getting-start example, maybe we should switch to the Ceph one (https://github.com/apache/polaris/blob/main/getting-started/ceph/docker-compose.yml) but updated it to match the same layout?
Thanks, Yong Zheng
