Map failing components to owning teams in CI failure notifications

[yulianedyalkova]

Motivation

When a test fails in CI, identifying which team should investigate requires some initial debugging, usually from Tenet. We're currently doing some heuristics but they're not very good and results in teams ignoring the pings. It would be perfect if we can automatically delegate to the right team and remove us as bottleneck.

Todo

• Audit what component signals crust-gather reliably surfaces (controller names, namespaces, CRDs, etc.)
• Map those signals to team ownership — determine where the source of truth for ownership lives (CODEOWNERS, a config file, Backstage, etc.)
• Integrate the mapping into the failure notification
• Include the owning team name in the #alert-ci post or thread reply (e.g. "Likely owner: team/batman")
• Define a fallback for unknown components - notify Tenet rather than silently dropping

Acceptance Criteria

• Failure notifications in #alert-ci include an owning team label for at least the most common failing components
• When no mapping is found, Tenet is notified as fallback and the unknown component is logged for future mapping