When a git tag is pushed to the bootc repo, a GitLab CI pipeline should:                                         

  1. Parse the tag to determine the version and target branch/application
  2. Query Konflux for snapshots matching the tagged commit SHA
  3. Determine the appropriate release plan for the application
  4. Generate Release CR YAML manifests
  5. Create an MR to the product-management-configs repo with the release files
  6. Send a notification that the release MR is ready for review

  This automates the manual process of creating release YAMLs and ensures releases are tied to a specific tagged
  commit.

  Open Questions (to resolve during implementation):
  - Do we want to look for releaseNotes or something?

  Acceptance Criteria:
  - Pushing a tag to the bootc repo triggers a pipeline that creates an MR in product-management-configs with valid
   Release CRs
  - The MR, once reviewed and merged, is picked up by the apply pipeline