[FEATURE]Align OTEL Traces index selection across all ingestion sinks

[YANG-DB]

Is your feature request related to a problem?
Today OTEL traces / Logs / Metrics can arrive from multiple ingestion vendors

• data-prepper
  • Metrics
  • Traces
  • Logs
• jaeger
  • Traces
• OTEL opensearch exporter (NEW)
  • Traces
  • Logs
• Flint
  • S3 trace bucket

---

The user has to explicitly be aware of the vendor's name and select the vendor instead of selecting the index that is the source of the traces data

What solution would you like?
We need a consolidated way to view traces regardless of their origin and allow the user to correctly view and select the index used for the traces store without explicitly knowing the ingestion pipeline identity

Instead of selecting the ingestion vendor name:

The user should not be aware of the ingestion vendor and only be able to select the index source for displaying the traces/services data - similar to the datasource widget

Do you have any additional context?

• https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/24668/files