[RFC] Disambiguous datasource for OSD developer and OSD plugin developer

[seraphjiang]

Today, there are two datasources in OSD which cause confusion.

One is direct datasource we introduced in 2.4, another is datasource introduced with observability which is not direct datasource in OSD. It won't work without observability plugin and a few backend plugin.

We propose only one data source concept in OSD, that means we need to centralized storage, management API, UI for the datasource.

Storage: the datasource meta info will be persist into .kibana or other supported meta storage

API: all datasource must be managed via saved-object API

Management UI: all datasource must be managed via DataSource management in Dashboards Management.
e.g.
https://playground.opensearch.org/app/management/opensearch-dashboards/dataSources

Below is the tasks to track the effort to fix the issue across opensource project

OSD:

• rename data/public/data_sources to Index-Pattern Selector
  https://github.com/opensearch-project/OpenSearch-Dashboards/tree/main/src/plugins/data/public/data_sources

• rename the data_source_management/public/components/cluster_selector to DataSource Selector [MD] Change name of data source picker from cluster selector #6038

Observability:
Move the observability datasource management from top left nav menu, it should move into observability dedicated page for short term. for long term, it should rewrite and merge into dashboards's build in datasource management. tracking progress here
opensearch-project/dashboards-observability#1469

[ashwin-pc]

@seraphjiang can you give some context as to why you opened this and why the name here differs from the one that @dagneyb proposed and the others aligned to? cc: @kgcreative

Original proposed names: #5790 (comment)

[seraphjiang]

@seraphjiang can you give some context as to why you opened this and why the name here differs from the one that @dagneyb proposed and the others aligned to? cc: @kgcreative

Original proposed names: #5790 (comment)

Already provided context. We will only has one datasource introduced from 2.4

Please check my comment, 'connection' is not right term. However that discussion is to seek alignment for end user. We could get more input. Especially from end user, not developers.

This proposal is to disambiguous for developer.