[ResponseOps] Lazy load dataViews and wrappedSearchSourceClient services when running alerting rules

[doakalexi]

Resolves #184322

Summary

This PR updates getExecutorServices to allow alerting rules to only load the dataViews and wrappedSearchSourceClient services when needed. I updated the rule types dependent on dataViews and/or wrappedSearchSourceClient.

Checklist

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

To verify

• Verify that the dataviews and searchsource are only loaded when needed. I think the best way to verify this is create an Index threshold rule and make sure that the dataViews and searchSourceClient services are not created.
• Verify that the updated rules work correctly. I updated the following rule types:
  Custom threshold
  SLO burn rate
  ES query
  Indicator match

[doakalexi]

/ci

[doakalexi]

/ci

[doakalexi]

/ci

[doakalexi]

/ci

[doakalexi]

/ci

[doakalexi]

/ci

[elasticmachine]

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

[dominiqueclarke]

Obs ux management changes LGTM.

[elasticmachine]

Pinging @elastic/obs-ux-management-team (Team:obs-ux-management)

[nkhristinin]

DE changes LGTM

[ymao1]

LGTM! Verified that all the impacted rule types ran and generated alerts. Looked at the APM transactions and saw the decrease in transaction latency! 🎉

Before:

After:

Interesting that the ES query latency improved as well even though it is still calling both functions.

[kibana-ci]

💚 Build Succeeded

• Buildkite Build
• Commit: dc60120
• Kibana Serverless Image: docker.elastic.co/kibana-ci/kibana-serverless:pr-189929-dc60120f69dc

Metrics [docs]

✅ unchanged

History

• 💛 Build #228261 was flaky 1997649
• 💛 Build #227119 was flaky 47f14ab
• 💚 Build #226616 succeeded e620f7e
• 💛 Build #226400 was flaky e620f7e
• 💔 Build #226385 failed 0bd9565

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