Add registry providers for APM data

[sorenlouv]

Follow-up to #244702

This adds data providers for APM data used in the old contextual insights API (/internal/observability/assistant/alert_details_contextual_insights). To avoid using that API for the new AI insights we should have a new API that cherry picks the data it needs

APM data can now be retrieved in the observability_agent plugin without depending on the APM plugin like:

this.dataRegistry.getData('apmServiceSummary', {
  request,
  serviceName,
  serviceEnvironment,
  start,
  end,
  transactionType,
});

[elasticmachine]

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

[rmyz]

small comment

[rmyz]

LGTM

[yuliia-fryshko]

APM data can now be retrieved in the observability_agent plugin without depending on the APM plugin like:

this.dataRegistry.getData('apmServiceSummary', {
request,
serviceName,
serviceEnvironment,
start,
end,
transactionType,
});

I think it will be more clean to use constants instead of string like apmServiceSummary. We could add them in observability_agent/common folder . Not blocking, just a thought :)

Otherwise, it looks nice. Thank you for making this change

[elasticmachine]

💛 Build succeeded, but was flaky

• Buildkite Build
• Commit: 96c61fb

Failed CI Steps

• Jest Integration Tests #4

Metrics [docs]

Public APIs missing exports

Total count of every type that is part of your API that should be exported but is not. This will cause broken links in the API documentation system. Target amount is 0. Run node scripts/build_api_docs --plugin [yourplugin] --stats exports for more detailed information.

id	before	after	diff
observabilityAgent	0	1	+1

History

• 💔 Build #367927 failed a819243
• 💔 Build #367849 failed a38a1d5
• 💔 Build #367795 failed 1224fce
• 💔 Build #367742 failed 259c2d4
• 💔 Build #367724 failed 940580f
• 💔 Build #367643 failed 56343b0