[Cases] Make the alerts table in cases GA

[cnasikas]

Summary

Security solution changed recently their alert tables to the alert table provided by ResponseOps. For this reason, I removed the experimental badge from the cases alerts table in the security solution and mark it as GA.

For maintainers

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

[elasticmachine]

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

[elasticmachine]

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

[cnasikas]

@elasticmachine merge upstream

[cnasikas]

@elasticmachine merge upstream

[cnasikas]

@elasticmachine merge upstream

[kibana-ci]

💛 Build succeeded, but was flaky

• Buildkite Build
• Commit: cd5136f

Failed CI Steps

• Security Solution Tests #2

Test Failures

• [job] [logs] Security Solution Tests #2 / Detection rules, bulk edit of rule actions Restricted action privileges User with no privileges can't add rule actions

Metrics [docs]

Unknown metric groups

ESLint disabled line counts

id	before	after	diff
securitySolution	433	436	+3

Total ESLint disabled count

id	before	after	diff
securitySolution	513	516	+3

History

• 💔 Build #118701 failed 0f9ddc3
• 💔 Build #118620 failed c54861b
• 💔 Build #118536 failed e976902

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

cc @cnasikas

[semd]

LGTM!
Will we do another iteration to remove the isExperimental flag and the dead code?

[cnasikas]

LGTM! Will we do another iteration to remove the isExperimental flag and the dead code?

Thanks, Sergi! If you mean inside the cases' code, no because we would need it for cases in the stack management in the future.