[UX] Use components from Exploratory View app in UX

[CoenWarmer]

Resolves #154053

📝 Summary

Now that the Exploratory View route is placed in its own application, the UX app can safely use components related to the Exploratory View from that application.

✅ Acceptance Criteria

• UX app should behave and function exactly the same as before.

[elasticmachine]

Pinging @elastic/uptime (Team:uptime)

[apmmachine]

🤖 GitHub comments

Expand to view the GitHub comments

Just comment with:

• /oblt-deploy : Deploy a Kibana instance using the Observability test environments.
• run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

[kibana-ci]

💚 Build Succeeded

• Buildkite Build
• Commit: ad4af06

Metrics [docs]

Module Count

Fewer modules leads to a faster build time

id	before	after	diff
ux	141	142	+1

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
exploratoryView	339	349	+10

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id	before	after	diff
ux	160.8KB	161.0KB	+158.0B

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
exploratoryView	17	22	+5

Page load bundle

Size of the bundles that are downloaded on every page load. Target size is below 100kb

id	before	after	diff
exploratoryView	58.6KB	59.6KB	+1.0KB

Unknown metric groups

API count

id	before	after	diff
exploratoryView	342	352	+10

ESLint disabled line counts

id	before	after	diff
securitySolution	432	435	+3

Total ESLint disabled count

id	before	after	diff
securitySolution	512	515	+3

History

• 💔 Build #116761 failed 1e3c4c8

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

[shahzad31]

these components belong in shared place in observability in my opinion. They are not part of exp view and are used in other places as well.

[CoenWarmer]

These components are not used in any app other than Ux and Synthetics, and when these apps use them, they only use them in the context of the Exploratory View feature.

Therefore it makes sense to keep them close to the Exploratory View app, where they are used. Alternatively, they could be stored in Ux, in Synthetics or a package that these apps share.

By keeping them in the Exploratory View application, the Synthetics team has full freedom to develop them further, and make sure they work correctly within the context of the Exploratory View app.

[shahzad31]

why not remove it?

[CoenWarmer]

I will in a following PR. Removing it in this PR means removing files owned by Ops, which will slow down this review.

[shahzad31]

App still seems to be working fine

though it's doing a full page when user is trying to dig deep into exploratory view embeddable via explore button

[kdelemme]

LGTM!