[Dataset Quality] Refactor integrations in DQ Flyout to not depend on main DQ Page page

[achyutjhunjhunwala]

Summary

This PR is a prerequisite to the Locator Implementation for Logs Explorer - #186287

Problem Statement

• Integrations were fetched when the main DQ page loads and stored in the State Machine. This means when the Flyout Opens, it was referencing already fetched data from the main page, updating the URL and then that was used to render certain sections on the Flyout. This causes issues as when a Locator is used to directly open the Flyout from some other page. In that case everything happen asynchronously causing the data to be not present when the flyout open thus those integration sections were not present.

Solution

• Now when the flyout is opened or is already open, it reads the basic params from the URL like DataStream. With this information, it make API call to fetch Integration information and thus making it independent.
  • Does this means you duplicated the Logic to fetch Integrations ? Yes and No. Logic has to be duplicated as Flyout is moving to its own page very soon. This means it would anyhow not be able to re-use that Integration Information available. Secondly the duplication is not one to one, its more catered towards Flyout logic
• Split the state machine to make Integration Calls only when the opened Dataset is actually an integration. This is done by chaining the respective states after the DataStreamSettings state confirms presence of Integration.

What else has been done

• Type cleaning: A lot of types has to be refactored to make this change. Also simplified some duplicate types. We were using
  • Runtime types
  • Types Derived from Runtime Types
  • Inferred Types from API Responses
    We don't need the 3rd one. 1 and 2 and sufficient.

[elasticmachine]

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

[obltmachine]

🤖 GitHub comments

Expand to view the GitHub comments

Just comment with:

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

[yngrdyn]

LGTM 🚀

[elasticmachine]

💛 Build succeeded, but was flaky

• Buildkite Build
• Commit: 2c42112
• Kibana Serverless Image: docker.elastic.co/kibana-ci/kibana-serverless:pr-187450-2c4211211a7d
• Observability Deployment

Failed CI Steps

Metrics [docs]

Async chunks

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

id	before	after	diff
datasetQuality	280.4KB	282.2KB	+1.8KB

Page load bundle

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

id	before	after	diff
datasetQuality	45.6KB	46.0KB	+339.0B

History

• 💔 Build #219452 failed 719fc1d
• 💛 Build #219422 was flaky 4171d8e
• 💔 Build #219386 failed 35e6f93
• 💔 Build #219371 failed f9dd8ee

cc @achyutjhunjhunwala