Make non-ResponseOps owned rule types flag user errors

[mikecote]

Blocked on: https://github.com/elastic/kibana/issues/180963

We should reach out to the owning teams of the rule types used in serverless (most listed below) and make them report user errors accordingly. They must follow the guidelines from https://github.com/elastic/kibana/issues/180963 to properly flag user type errors.

Rule Types:

• [ ] Transform health
• [ ] Tracking containment
• [ ] Custom threshold
• [ ] SLO burn rate
• [ ] Anomaly detection
• [ ] Anomaly detection jobs health
• [ ] Inventory
• [ ] Latency threshold
• [ ] APM Anomaly
• [ ] Error count threshold
• [ ] Failed transaction rate threshold
• [ ] Event Correlation Rule
• [ ] ES|QL Rule
• [ ] Saved Query Rule
• [ ] Indicator Match Rule
• [ ] Machine Learning Rule
• [ ] Custom Query Rule
• [ ] Threshold Rule
• [ ] New Terms Rule
• [ ] Security Solution notification (Legacy)
• [ ] ... see if there are more (serverless only) ...

Definition of Done

• [ ] All owning teams have GitHub issues requesting them to flag user type errors accordingly
• [ ] GitHub issues reference our guidelines
• [ ] Checked to see if there are more rule types missing in this list (serverless rule types only)

[elasticmachine]

Pinging @elastic/response-ops (Team:ResponseOps)