[Cases] Handle undefined connectors config field

[jonathan-buttner]

This fixes an issue where Cases will crash the UI when determining if a connector is deprecated. This is because we attempt to read from the config property on a connector and the property might be undefined. config is undefined when the connector is pre-configured. If a connector doesn't leverage the config field it will be an empty object.

For more details see: #119696

I filter out the connectors do not have the config field defined or are marked as PreConfigured: true.

Cases will not show the connectors as options to select.

Slack has an empty config

Cases doesn't show the preconfigured connectors

To test this you can define the following in your config/kibana.dev.yml

xpack.actions.preconfigured:
  my-servicenow:
    name: preconfigured-servicenow-sir-connector-type
    actionTypeId: .servicenow-sir
    config:
      usesTableApi: true
      apiUrl: https://testservicenow
      hasAuth: true

Release Notes

Pre-configured connectors cannot be used within Cases.

cc: @YulNaumenko

[elasticmachine]

Pinging @elastic/security-threat-hunting-cases (Team:Threat Hunting:Cases)

[jonathan-buttner]

@elasticmachine merge upstream

[cnasikas]

@elasticmachine merge upstream

[jonathan-buttner]

I'm exporting this so I can test it directly 😬 I could test via the createConfigurationSubClient but it's a little more difficult.

[kibana-ci]

💚 Build Succeeded

• Buildkite Build
• Commit: 748e46e
• Storybooks Preview

Metrics [docs]

✅ unchanged

History

• 💚 Build #12782 succeeded 66d609b
• 💚 Build #12130 succeeded 38a35aa
• 💔 Build #11950 failed 3a8164b

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

[kibanamachine]

💚 Backport successful

Status	Branch	Result
✅	8.0
✅	7.17

The backport PRs will be merged automatically after passing CI.