Increase RCA agent timeout to 10 minutes for deep analysis

Change RCA_AGENT_TIMEOUT_SECONDS from 120s (2 min) to 600s (10 min)
to allow agents sufficient time for thorough investigation:
- Code Archaeologist: git blame, PR analysis, test change detection
- Infrastructure Detective: pattern matching, flake classification
- Cross-Issue Correlator: JIRA searches, frequency analysis

Also increase aggregation timeout from 30s to 60s.

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>

Author: janisz

workflows/acs-triage/reference/constants.md

@@ -115,8 +115,8 @@ Central location for all hardcoded values used throughout the ACS triage workflo
 
 | Constant | Value | Purpose |
 |----------|-------|---------|
-| RCA_AGENT_TIMEOUT_SECONDS | 120 | Max time per agent |
-| RCA_AGGREGATION_TIMEOUT_SECONDS | 30 | Max time for findings aggregation |
+| RCA_AGENT_TIMEOUT_SECONDS | 600 | Max time per agent (10 minutes for deep analysis) |
+| RCA_AGGREGATION_TIMEOUT_SECONDS | 60 | Max time for findings aggregation |
 | RCA_TEAM_PREFIX | "ci-rca-" | Team name prefix for RCA teams (e.g., "ci-rca-ROX-12345") |
 | MIN_SIMILARITY_THRESHOLD | 0.70 | Min similarity (70%) for including historical issues in correlation results |
 | VERY_SIMILAR_THRESHOLD | 0.85 | Similarity threshold (85%) for "very similar" classification |