[ResponseOps][Connectors] Mark TCP connection errors as user errors #248225
Description
Summary
A single project triggered one of our SLOs with the following error:
Action '131bb1e1-8583-44d9-9923-2ce26429096e' failed: an error occurred while running the action: [Action][Jira]: Unable to create incident. Error: Client network socket disconnected before secure TLS connection was established. Reason: unknown: errorResponse was null
This was diagnosed as a user issue, and we introduced an exclusion for this project.
The long-term fix is to mark these errors as user-errors so the SLO can ignore them.
Once that is done, the changes in this PR - https://github.com/elastic/kibana-o11y-resources/pull/151 - should be reverted.
More information can be found in https://elasticco.atlassian.net/issues?filter=15239&selectedIssue=APEX-200