[WIP] Add dataset select and service to explore

[kavilla]

Description

TODO

• Update the buttons to open the explore view where users can select data without creating an index pattern
• some minor UX touchups
• remove the label dataset
• recent datasets

#10014

The dataset select component alongside the data view service.

NOTE: This is the initial foundational work. Will clean up unused and make it more unique to datasets but people can review this PR under the assumption this is similar to index patterns

The original PR: #9980 had conflicts with namespacing that typescript was getting thrown off. It had conflicts with the existing dataset and the dataset interface in the query does not nicely confirm to index pattern. The next logical namespace for me was data view which is a view of the data.

So data view acts as a direct fork of index pattern to avoid backwards compatibility issues for existing index patterns and to not break the query enhancements logic.

This also includes the change to run story book on a multiple ports. Since the storybook for this plugin is not the explore plugin I wanted the ability to run the storybook for each plugin not just one at a time.

Issues Resolved

#9791

Screenshot

Testing the changes

Changelog

Check List

• All tests pass
  • yarn test:jest
  • yarn test:jest_integration
• New functionality includes testing.
• New functionality has been documented.
• Update CHANGELOG.md
• Commits are signed per the DCO using --signoff

[github-actions]

❌ Empty Changelog Section

The Changelog section in your PR description is empty. Please add a valid changelog entry or entries. If you did add a changelog entry, check to make sure that it was not accidentally included inside the comment block in the Changelog section.

[github-actions]

❌ Empty Changelog Section

The Changelog section in your PR description is empty. Please add a valid changelog entry or entries. If you did add a changelog entry, check to make sure that it was not accidentally included inside the comment block in the Changelog section.

[github-actions]

❌ Empty Changelog Section

The Changelog section in your PR description is empty. Please add a valid changelog entry or entries. If you did add a changelog entry, check to make sure that it was not accidentally included inside the comment block in the Changelog section.

[github-actions]

❌ Empty Changelog Section

The Changelog section in your PR description is empty. Please add a valid changelog entry or entries. If you did add a changelog entry, check to make sure that it was not accidentally included inside the comment block in the Changelog section.

[kavilla]

• label for select component should be Data temporarily
• in the future, the temp dataset created in the saved search should be translated to using the virtual all dataset object. if i find if that not to be compat with specific data sources then we should bring it up
• single button dont show manage and create
• re-add recent datasets
• for details use the description component
• selector text to be smaller
• change timefield in details not be selector
• Manage for the dataset details iif index pattern
• datasetdetails data definition on click takes you to the appropriate view like data source or index pattern

[kamingleung]

• In the three-dot menu, consider using description list component for displaying the meta information. Remove the borders
• Consider removing the icons and show a check on the selected item: see single selectable
• In the three-dot menu, If the timefield is read-only, show as key-value text. Avoid using disabled dropdown.

[github-actions]

❌ Empty Changelog Section

The Changelog section in your PR description is empty. Please add a valid changelog entry or entries. If you did add a changelog entry, check to make sure that it was not accidentally included inside the comment block in the Changelog section.

[kamingleung]

• The dropdown width should be fixed, it shouldn't resize based on the text width. We should truncate the text if it's too long to fit the dropdown:

• Hide the "Default" badge if the dataset is not a default dataset:

• When user is viewing a default dataset, the badge should not be clickable or focusable, it's read-only: