[Discover] Add context awareness telemetry tests for Observability profiles

[davismcphee]

Summary

As suggested in https://github.com/elastic/kibana/pull/199255#discussion_r1842804292, I've copied and modified the existing Discover context awareness telemetry tests to work for Observability profiles. This helps test that solution root profiles are picked up as expected, as well as giving us some serverless coverage.

@elastic/appex-qa It didn't seem like there were any config specific services for serverless tests yet, so I added the EBT to services to the main serverless config. If there's a better way to do this, please let me know and I can update it.

Checklist

• [ ] 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
• [x] Unit or functional tests were updated or added to match the most common scenarios
• [ ] If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the docker list
• [ ] This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The release_note:breaking label should be applied in these situations.
• [ ] Flaky Test Runner was used on any tests changed
• [ ] The PR description includes the appropriate Release Notes section, and the correct release_note:* label is applied per the guidelines

[elasticmachine]

:robot: Jobs for this PR can be triggered through checkboxes. :construction: :information_source: To trigger the CI, please tick the checkbox below :point_down: - [ ] Click to trigger **kibana-pull-request** for this PR! - [ ] Click to trigger **kibana-deploy-project-from-pr** for this PR!

[elasticmachine]

:broken_heart: Build Failed

• Buildkite Build
• Commit: 50f5f6659e0c841b8abdbd951b81e5afb7f8e694

Failed CI Steps

• FTR Configs #64
• FTR Configs #64

Test Failures

• [job] [logs] FTR Configs #64 / serverless observability UI discover/observabilitySolution/context_awareness telemetry events should track field usage when a field is removed from the table
• [job] [logs] FTR Configs #64 / serverless observability UI discover/observabilitySolution/context_awareness telemetry events should track field usage when a field is removed from the table

Metrics [docs]

✅ unchanged

History

cc @davismcphee