[Cases] Fix connector's icon bug

[cnasikas]

Summary

The triggersActionsUi provides access to the actionTypeRegistry. Cases use the actionTypeRegistry to get the icon of the connector. If the type of the connector is not registered to the actionTypeRegistry an error will be thrown if you try to get the action type from the registry. The error is not being handled properly by Cases leading to broken Kibana.

Steps to reproduce:

1. Create a case.
2. Push it to an external service like Jira.
3. Change the connector to none.
4. Go back to the All cases page.

You should see the following error:

Also, the connector icon being shown on the All cases page is wrong. The page shows the icon of the connector that is selected for the particular case and that of the last pushed connector.

Steps to reproduce:

1. Create a case.
2. Push it to SN.
3. Change the connector to Jira.
4. Go back to the All cases page.

You should see the Jira icon instead of the SN icon. Example:

This PR fixes both bugs.

Checklist

Delete any items that are not applicable to this PR.

• Unit or functional tests were updated or added to match the most common scenarios

For maintainers

• This was checked for breaking API changes and was labeled appropriately

[elasticmachine]

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

[kibanamachine]

💚 Build Succeeded

• continuous-integration/kibana-ci/pull-request
• Commit: 40d23d3
• Storybooks Preview

Metrics [docs]

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id	before	after	diff
cases	529.0KB	579.6KB	+50.6KB

Page load bundle

Size of the bundles that are downloaded on every page load. Target size is below 100kb

id	before	after	diff
cases	131.7KB	131.7KB	-66.0B

Unknown metric groups

async chunk count

id	before	after	diff
cases	15	14	-1

History

• 💔 Build #142913 failed dd15690

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

cc @cnasikas