[jaeger-v2] Refactor ElasticSearch/OpenSearch Storage Configurations

[mahadzaryab1]

Requirement

In this issue, we want to align the configuration for elastic search and open search storage with OTEL (part of #5229)

Problem

• All config fields are tagged with mapstructure such that they can be addressable from YAML via "good" names
• Configs implement Validate()
• Configs via YAML support the same defaults as in jaeger-v1
• Configs reuse standard elements of OTEL configs whenever possible, e.g. TLS, clientcfg, etc.
• Configuration looks "logical" and properly grouped, not flattened with long weird names
• We create a migration guide document with a table that lists v1 CLI flags and the corresponding v2 config fields

[mahadzaryab1]

@yurishkuro is a migration guide needed here?

[yurishkuro]

yes, certainly