Add metrics to retry_stuck_testcases cronjob
This change adds metrics to the retry_stuck_testcases cronjob to provide better visibility into its operation. The new metrics track the number of testcase candidates and the various outcomes of the process, such as successful restarts and different reasons for skipping. These metrics are also collected during --dry-run executions to allow for safe monitoring and analysis.
PR created automatically by Jules for task 17630666630767645746
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.
When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.
I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!
For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!
For security, I will only act on instructions from the user who triggered this task.
/gcbrun
This pull request has not had any activity for 60 days and will be automatically closed in two weeks