StatusCode-Based Stop Condition Filtering for Triggered Diagnosis Loops

Today, the Stop When condition for a Repeat Triggered Diagnosis loop can only halt execution based on a generic alert detection result. It cannot distinguish between different diagnosis outcomes using StatusCode-based filtering, so a loop cannot be configured to stop specifically on a SUCCESS result in addition to an ALERT result. This enhancement would allow the Stop When condition to filter on specific StatusCode values, enabling the loop to stop and trigger a Follow-up Triggered Diagnosis action whether the diagnosis returns ALERT or SUCCESS. Supporting both outcomes would let diagnostic logic and business notification actions remain cleanly separated, allowing tickets to be automatically escalated for human follow-up on critical conditions or closed automatically once conditions resolve, without manual intervention.