[ResponseOps] Adds uiSettingsClient to alerting framework services

[dplumlee]

Summary

Related to #64588 and brought up in this (much more recent) PR comment

Some of the plugins that use the alerting framework plugin (such as the security solution) require access to kibana's ui advanced settings on the backend. Previously this had been achieved by using the uiSettings config off the savedObjectsClient directly but as stated in the above comment, this is not a best practice approach as the location/format of the config is subject to change.

This PR adds the uiSettingsClient from the kibana core start service and passes it down through to the alerting framework services which then allows it to be consumed and utilized by dependent features such as the security solution rule executors.

Checklist

Delete any items that are not applicable to this PR.

• Documentation was added for features that require explanation or tutorials
• Unit or functional tests were updated or added to match the most common scenarios

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

[elasticmachine]

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

[elasticmachine]

Pinging @elastic/security-detections-response (Team:Detections and Resp)

[kibana-ci]

💛 Build succeeded, but was flaky

• Buildkite Build
• Commit: 620e779
• Storybooks Preview
• Webpack Bundle Analyzer

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	292	293	+1

Unknown metric groups

API count

id	before	after	diff
alerting	300	301	+1

History

• 💔 Build #27003 failed 2e9433e
• 💔 Build #26990 failed 46d32f0
• 💔 Build #26983 failed 844b10b
• 💔 Build #26962 failed 2dff7ae0f359a465af98aef4d57694865b7cd114

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

cc @dplumlee

[ymao1]

LGTM! Thanks for adding this!

[kibanamachine]

💔 Backport failed

The pull request could not be backported due to the following error:
There are no branches to backport to. Aborting.

How to fix

Re-run the backport manually:

node scripts/backport --pr 126648

Questions ?

Please refer to the Backport tool documentation

[kibanamachine]

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create backports run node scripts/backport --pr 126648 or prevent reminders by adding the backport:skip label.

[kibanamachine]

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create backports run node scripts/backport --pr 126648 or prevent reminders by adding the backport:skip label.