[RAM][Security Solution][Alerts] moves legacy actions migration to rulesClient using hook in rules type definition

[vitaliidm]

Summary

• addresses [RAM][SECURITY SOLUTION][ALERTS] Research on migrating security legacy action inside of rule client #151919

Checklist

Delete any items that are not applicable to this PR.

• Any text added follows EUI's writing guidelines, uses sentence case text and includes i18n support
• Documentation was added for features that require explanation or tutorials
• Unit or functional tests were updated or added to match the most common scenarios
• Any UI touched in this PR is usable by keyboard only (learn more about keyboard accessibility)
• Any UI touched in this PR does not create any new axe failures (run axe in browser: FF, Chrome)
• If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the docker list
• This renders correctly on smaller devices using a responsive layout. (You can test this in your browser)
• This was checked for cross-browser compatibility

Risk Matrix

Delete this section if it is not applicable to this PR.

Before closing this PR, invite QA, stakeholders, and other developers to identify risks that should be tested prior to the change/feature release.

When forming the risk matrix, consider some of the following examples and how they may potentially impact the change:

Risk	Probability	Severity	Mitigation/Notes
Multiple Spaces—unexpected behavior in non-default Kibana Space.	Low	High	Integration tests will verify that all features are still supported in non-default Kibana Space and when user switches between spaces.
Multiple nodes—Elasticsearch polling might have race conditions when multiple Kibana nodes are polling for the same tasks.	High	Low	Tasks are idempotent, so executing them multiple times will not result in logical error, but will degrade performance. To test for this case we add plenty of unit tests around this logic and document manual testing procedure.
Code should gracefully handle cases when feature X or plugin Y are disabled.	Medium	High	Unit tests will verify that any feature flag or plugin combination still results in our service operational.
See more potential risk examples

For maintainers

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

[vitaliidm]

@elasticmachine merge upstream

[kibanamachine]

merge conflict between base and head

[vitaliidm]

Leaving this PR for historical and tracking purposes as POC of moving legacy migration to rulesClient through hook in rule type definition.

Further work, will be done in #153101, which is based on this, but migration will be implemented directly in RulesClient instead of passing as hook

[kibana-ci]

💔 Build Failed

• Buildkite Build
• Commit: 889e983
• Interpreting CI Failures

Failed CI Steps

• Jest Tests #8
• Security Solution Tests #4

Test Failures

• [job] [logs] Security Solution Tests #4 / Exceptions flyout "after each" hook for "Warns users about mapping conflicts on problematic field selection"
• [job] [logs] Jest Tests #8 / rules_client_conflict_retries 1 retry works for method update
• [job] [logs] Jest Tests #8 / rules_client_conflict_retries 3 retries fails with conflict error update

Metrics [docs]

Public APIs missing comments

Total count of every public API that lacks a comment. Target amount is 0. Run node scripts/build_api_docs --plugin [yourplugin] --stats comments for more detailed information.

id	before	after	diff
alerting	515	523	+8

Unknown metric groups

API count

id	before	after	diff
alerting	531	539	+8

ESLint disabled line counts

id	before	after	diff
securitySolution	432	416	-16

Total ESLint disabled count

id	before	after	diff
securitySolution	509	493	-16

History

• 💛 Build #113007 was flaky ba07da5
• 💛 Build #112959 was flaky b110f13
• 💔 Build #112693 failed 97382e4
• 💔 Build #112508 failed ac8f04c

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

cc @vitaliidm