[CS for Registry] Limit Scans for Registry
What does this MR do and why?
The feature triggers a pipeline whenever an image is pushed (currently with the latest tag), which may lead to performance issues such as a high volume of SBOM reports being ingested into the database. This is primarily a concern because we do not remove/replace the old report when a new image is pushed.
Limit the automated CS scans to 50 per day per project.
MR acceptance checklist
Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
Related to #462366 (closed)