Adds an execution Error Code to Flakeguard

[kalverra]

New error code for Flakeguard to help us identify when we find flakes, or when we hit errors finding flakes.

Exit Code 1: Flakeguard ran successfully and found some flakes
Exit Code 2: Flakeguard hit some issues and was not able to complete

---

Below is a summarization created by an LLM (gpt-4-0125-preview). Be mindful of hallucinations and verify accuracy.

Why

The changes introduce enhancements and bug fixes to various commands in the Flakeguard tool suite, focusing on error handling, logging improvements, and exit code standardization. These modifications aim to make the tool more robust and user-friendly by providing clearer error messages, ensuring consistent exit behavior across commands, and improving the overall reliability and maintainability of the codebase.

What

• tools/flakeguard/cmd/aggregate_results.go:
  • Import "os" for exit code management and error handling.
  • Replace RunE with Run to manage errors and exit codes manually.
  • Use log.Error() and os.Exit() for error handling, improving clarity and control over exit behavior.
  • Remove redundant error checks and stop spinners more reliably.
• tools/flakeguard/cmd/check_test_owners.go:
  • Import "os" for handling exit codes.
  • Replace RunE with Run for manual error and exit code management.
  • Use log.Error() and os.Exit() for error handling.
• tools/flakeguard/cmd/find.go:
  • Import "os" for improved error and exit code handling.
  • Transition to Run from RunE and manage errors and exit codes manually.
  • Use log.Error() and os.Exit() for error handling.
  • Adjust logging and error handling for consistency and clarity.
• tools/flakeguard/cmd/generate_report.go:
  • Import "os" for enhanced error handling and exit code management.
  • Shift from RunE to Run to manually handle errors and exit codes.
  • Apply log.Error() and os.Exit() for error handling, enhancing clarity.
  • Improve error messaging and exit strategy for a user-friendly interface.
• tools/flakeguard/cmd/run.go:
  • Define constants FlakyTestsExitCode and ErrorExitCode for standardized exit codes.
  • Utilize Run instead of RunE for explicit error and exit code control.
  • Implement log.Error() and os.Exit() for uniform error handling.
  • Clarify and standardize error and exit code handling for reliability.
• tools/flakeguard/reports/presentation.go:
  • Introduce RenderError function for consistent error reporting.
• tools/flakeguard/runner/runner_test.go:
  • Minor text adjustment in a comment for clarity.

[cl-sonarqube-production]

Quality Gate failed

Failed conditions
6.8% Duplication on New Code (required ≤ 5%)

See analysis details on SonarQube