Feature title:  Automate Updates to the Packages in the Package Index

Feature Overview:
We want to run regular automated updates to pull new versions of packages that we build to ensure our teams and customers have access to the latest content.

Product(s) associated:

RHAIIS: yes
RHEL AI: yes
RHOAI: yes

Goals:

• Automated updates in the main branch of the testcollections repo for the test index, triggered based on a schedule and possibly based on events that recognize a new package is available.
• Monitoring of notifications and prioritization of build issues in the testcollection pipelines.
• Automated updates in the main development index, triggered based on a schedule and possibly based on events that recognize a new package is available.
• Automated updates in the z-stream indexes, with more controlled sets of packages being updated.
• Track the lead time from a package being released to our build system trying to build it.

Requirements:

• New releases of common and easy to build packages should be added to the index automatically.
• New releases of hard to build packages should be added to the index, or if they fail to build a Jira ticket should be created to track the need to fix the build.
• We need to decide how best to manage updates in z-stream indexes.

Done - Acceptance Criteria:

• We update the testcollection index daily.
• We have a process in place for monitoring and responding to build failures in the test collection, including Jira tickets and team processes for triaging and prioritizing nightly build failures over other work.
• We update the development index daily.
• We update the z-stream indexes at least once for each z-stream release, before the images for the release are built so they can consume the new packages.

Use Cases - i.e. User Experience & Workflow:
Include use case diagrams, main success scenarios, alternative flow scenarios.

Out of Scope:
High-level list of items or personas that are out of scope.

Documentation Considerations :
Provide information that needs to be considered and planned so that documentation will meet customer needs. If the feature extends existing functionality, provide a link to its current documentation.