[jaeger-v2] Decide how different configurations will be provided to the users

[yurishkuro]

In v1 we published different binaries that exposed different configurations via CLI flags. In v2 we only have a single binary that can be made to work differently depending on the configuration file. The question is - how will we guide the users to the appropriate configuration file? There are multiple concerns here:

• illustrating how a specific deployment unit, e.g. ingester, can be configured
• illustrating which configuration options exist for each component (OTEL Collector currently has readme's for each component, but they vary in quality, and so far there is no schema-first solution for exhaustive config documentation as we had with Jaeger v1)
  • Issue Print final configuration open-telemetry/opentelemetry-collector#1791 is stuck, it could've addressed this point. We could implement our own version just for the Jaeger components

Currently we only have one explicit config file (which in practice implements all-in-one binary).

Some options:

• provide a single mega-config that includes all possible modes but comments them out
• provide individual configs for each binary as is done in [jaeger-v2] Add kafka exporter and receiver configuration #4971
  • the downside of this is the different configs won't be kept in sync
• create config snippets for different modes that can be included into one config

[yurishkuro]

@james-ryans curious if you have any thoughts