Feat: Integrate Triage Dashboard for Flake Detection

[knabben]

Description

The handbook recommends using Triage dashboard to analyze flake patterns across different jobs. Currently, signalhound only uses TestGrid data for flake detection, which may not provide complete flake rate information.

Requirements

• Integrate with Triage dashboard API
• Calculate flake rates across multiple jobs
• Identify flake patterns (time-based, job-specific, etc.)
• Use Triage data to enhance flake detection accuracy
• Display flake rate information in TUI

Acceptance Criteria

• Triage API integration for flake rate calculation
• Flake rates are calculated across multiple jobs
• Flake patterns are identified and reported
• Triage data enhances TestGrid flake detection
• Flake rate information is displayed in issue templates
• Unit tests for Triage integration
• Integration tests with Triage API

Implementation Notes

• Query Triage API: https://storage.googleapis.com/k8s-triage/index.html
• Calculate flake rate: flake_count / total_runs
• Analyze patterns across jobs and time periods
• Cache Triage data to reduce API calls

[knabben]

Related to #22

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale