[ResponseOps][Cases] Setting rule info to null for 8.0

[jonathan-buttner]

This is a manual "backport" of this PR: #123094

This is needed because there are multiple features/refactoring that did not go into 8.0.0 but are currently in 8.1. This will cause the above PR's backport to fail so I manually pulled in the changes file by file 😬

Testing

To test I would attach an alert to the case, then grab the alertId and case ID information to use with a postman request like this:

{
    "alertId": [<add a valid alertId here>],
    "index": [".internal.alerts-security.alerts-default-000001"],
    "rule": { "id": null, "name": null },
    "type": "alert",
    "owner": "securitySolution"
}

You should see the rule's name show up for both alerts and clicking on it should take you to the rule's page.

[academo]

nitpick: this kind of code can be confusing as items could be undefined and can also be null. I'd recommend the more verbose but clear and type safe way:

if (item === undefined || item === null) {

[jonathan-buttner]

@elasticmachine merge upstream

[elasticmachine]

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

[elasticmachine]

Pinging @elastic/response-ops-cases (Feature:Cases)

[cnasikas]

Tested by running a 7.16 instance and then upgrading to 8.0. All is working as expected. Thank you so much for the fix and the effort you put into it 🚀

[kibana-ci]

💚 Build Succeeded

• Buildkite Build
• Commit: b69125e
• 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	312.9KB	312.8KB	-60.0B

History

• 💔 Build #18081 failed 261a2a6
• 💚 Build #17811 succeeded f1f8124
• 💚 Build #17661 succeeded 31c1609

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