The failed-composes repository stores logs and metadata for compose failures and is referenced frequently by compose-tracker tooling and RelEng workflows. We need to migrate it as part of the RelEng sub-repository migration plan for Sprint 5.

This migration follows the same two-week timeline:

Week 1: Investigation
Week 2: Implementation

Phase 1: Investigation (Week 1)
Tasks:
- Review the structure of the repository, especially how data is stored.
- Identify all scripts and tools across RelEng that read/write to this repository.
- Check whether compose-tracker or Pungi tooling has hardcoded Pagure URLs.
- Review open issues and verify migration readiness.

Phase 2: Implementation (Week 2)
Tasks:
- Perform migration to Forgejo using migration tooling.
Validate:
- Directories and content structure
- Issue tracker migration
- Integration with compose tracking workflows
- Update scripts in releng/compose-tracker pointing to the new Forgejo repo.
- Disable Pagure repository and add README redirect.

Acceptance Criteria:
- All compose failure data preserved post-migration.
- No disruption in compose error reporting or automated detection.
- All references updated across RelEng.
- Pagure repository closed and redirected.