[APM][RUM] adjust data types for uiFilters and range in APM requests

[dominiqueclarke]

Summary

Fixes elastic/uptime-dev#56

This PR adjusts data type for the query in has_rum_data route.

This is primarily to resolve issues with the hasRumData route, the params for which can be entirely undefined.

const rumHasDataRoute = createApmServerRoute({
  endpoint: 'GET /api/apm/observability_overview/has_rum_data',
  params: t.partial({
    query: t.intersection([uiFiltersRt, rangeRt]),
  }),
  options: { tags: ['access:apm'] },
  handler: async (resources) => {
    const setup = await setupRequest(resources);
    return await hasRumData({ setup });
  },
});

In particular, the exploratory view uses this api route to dynamically fetch apm indicies, without passing any params. This caused the error Invalid value undefined supplied to : strict_keys/0: Partial<{ query: ({ uiFilters: string } & { start: isoToEpochRt, end: isoToEpochRt }) }>/query: ({ uiFilters: string } & { start: isoToEpochRt, end: isoToEpochRt })/0: { uiFilters: string }/uiFilters: string when debug settings were applied.

To test
For APM exploratory view data, it's best to point your local kibana to edge ES.
In the advanced settings, turn Observability debug on

Navigate to exploratory view using the "Analyze Data" button in User Experience or Uptime
Select the data type as "User Experience (RUM)".
Ensure that the two report types "KPI over time" and "Performance Distribution" appear, and that there are no errors from api calls in the network tab.

This API is also used by the Observability Overview page UX section. We should also smoke test that section to make sure it's still working.

[ ] Observability Overview UX page is still working in both debug and regular mode
[ ] Exploratory View "User Experience (RUM)" data type works in both debug and regular mode

[elasticmachine]

Pinging @elastic/apm-ui (Team:apm)

[elasticmachine]

Pinging @elastic/uptime (Team:uptime)

[dominiqueclarke]

@elasticmachine merge upstream

[dominiqueclarke]

@elasticmachine merge upstream

[cauemarcondes]

LGTM

[kibanamachine]

💚 Build Succeeded

• continuous-integration/kibana-ci/pull-request
• Commit: e91ddad
• Storybooks Preview

Metrics [docs]

Unknown metric groups

References to deprecated APIs

id	before	after	diff
canvas	29	25	-4
crossClusterReplication	8	6	-2
fleet	4	2	-2
globalSearch	4	2	-2
indexManagement	12	7	-5
infra	5	3	-2
licensing	18	15	-3
monitoring	109	56	-53
total			-73

History

• 💔 Build #126000 failed 65676a8
• 💔 Build #125994 failed 9eed989
• 💚 Build #125695 succeeded 0d334c8
• 💔 Build #125612 failed 2138cfa47d4cb2671ab9190eb9641dc4273d832f
• 💔 Build #125544 failed 5b58e20

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

[justinkambic]

LGTM!

[kibanamachine]

💚 Backport successful

Status	Branch	Result
✅	7.13
✅	7.x

The backport PRs will be merged automatically after passing CI.