Migrate Feast Release Images from Docker to Quay

[redhatHameed]

We are planning to migrate all Feast release images from Docker to Quay. This change is aimed at enhancing security, improving image management, and fix the issue for example rate limit .

We already have the quay place holder for Feast https://quay.io/feastdev

What is ​​Quay.io

Quay.io the container registry platform for managing the cloud native artifacts, where you can securely store, distribute, and deploy. We are transitioning to Quay due to the following advantages:

• Store containers securely
  Easily publish your container images or or store them privately with granular access control. Quay.io is optimized for open source project and enterprise users, with powerful flexible permission and tenancy model.

• Automated container build integration
  Use Quay.io to automate the container builds, with integration to GitHub, GitLab, and more. Robot accounts allow to lock down automated access and audit each deployment.

• Continually scan your containers for vulnerabilities
  Quay.io continually scans containers for vulnerabilities, giving real-time visibility into known issues and how to fix them.

• Free public download page for your container
  Provide a public download page for the container.

Impact on the Community:
Image pull URLs will change from Docker to Quay.
Documentation will be updated to reflect the new image registry locations.

Next Steps:

Update release pipelines to push images to Quay.
Modify relevant documentation and inform to community.

Further Read from below links

https://docs.redhat.com/en/documentation/red_hat_quay/3/html/about_quay_io/index

https://quay.io/repository/

[franciscojavierarceo]

Can we outline why we are using Quay please? Should be clear to users.