[Security Solution] Error when exporting a rule that has an action referencing a deleted connector

[maximpn]

Epics: https://github.com/elastic/security-team/issues/1974 (internal), #179907
Related to: #198771, #198845, https://github.com/elastic/security-team/issues/8816 (internal)

Summary

Rule export gets blocked whenever there is a rule with configured action (for example send message to Slack) which references a removed connector (for example Slack connector). Rule export fails with an error Error fetching objects to export instead of exporting a rule and display a warning message.

{
  "name": "Error",
  "body": {
    "message": "Error fetching objects to export",
    "status_code": 500
  },
  "message": "",
  "stack": "{\n  \"message\": \"Error fetching objects to export\",\n  \"status_code\": 500\n}"
}

Steps to reproduce

1. Create a rule, e.g. a custom query rule
2. Add an action to the rule (it requires to create a connector if non exists for the action type)
3. Delete the referenced connector
4. Export the rule with an action referencing deleted connector

Expected result:
Rule is exported without an action referencing deleted connector and a warning message is shown.

Actual result:
Rule export fails with an error

Needs product input on how to handle it. Should be consistent with #198771.

[elasticmachine]

Pinging @elastic/security-solution (Team: SecuritySolution)

[elasticmachine]

Pinging @elastic/security-detections-response (Team:Detections and Resp)

[elasticmachine]

Pinging @elastic/security-detection-rule-management (Team:Detection Rule Management)