[Unified observability] Extract ObservabilityIndexPatterns from exploratory view

[afgomez]

Summary

Part of #118242. Closes #120210

We want to use an embedded dashboard on the new overview page. Dashboards and Lens need to have a Kibana Data View to query the data.

The exploratory view has a mechanism to create data views on the fly and we want to reuse it. To do so we have done the following:

• Moved the code to a shared location.
• Refactor the deprecated indexPattern terminology, APIs and types.

[elasticmachine]

Pinging @elastic/unified-observability (Team:Unified observability)

[estermv]

LGTM!

[estermv]

After approving the PR, I thought a bit more about the new location... is it x-pack/plugins/observability/public/components/shared/ the best location for the ObservabilityDataViews, given that is not a component?

What do you think about moving it to the x-pack/plugins/observability/public/utils/ folder? Although I'm not a fan of the utils folders in general, it seems a more appropriate location.

[kibana-ci]

💚 Build Succeeded

• Buildkite Build
• Commit: 555b40d
• Storybooks Preview

Metrics [docs]

Module Count

Fewer modules leads to a faster build time

id	before	after	diff
observability	348	349	+1

Async chunks

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

id	before	after	diff
observability	357.8KB	357.8KB	-4.0B

Page load bundle

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

id	before	after	diff
observability	79.3KB	79.3KB	-44.0B

Unknown metric groups

References to deprecated APIs

id	before	after	diff
observability	155	132	-23

History

• 💚 Build #15668 succeeded 803e70b
• 💚 Build #15438 succeeded 3c77ca6
• 💔 Build #15334 failed f04575e

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

[lucasfcosta]

LGTM. Also, agree with @estermv, x-pack/plugins/observability/public/utils/ seems to be the right place for these files.

Also checked out the branch and navigated around just to be sure everything still looks okay.

[kibanamachine]

💔 Backport failed

The pull request could not be backported due to the following error:
There are no branches to backport to. Aborting.

How to fix

Re-run the backport manually:

node scripts/backport --pr 122132

Questions ?

Please refer to the Backport tool documentation