Create example configuration for jaeger-query v2

[yurishkuro]

Per https://github.com/orgs/jaegertracing/discussions/6682

Jaeger query as a role does not require the ingestion pipeline, only the query service, but the OTEL Collector architecture does not support that, it requires a minimum pipeline. OTEL Collector does provide nop receiver and exporter that can be used to define a dummy pipeline, but we did not import them in our components.go

• import nop receiver and exporter
• create a sample query service configuration
• extend our e2e integration tests to exercise this new configuration (the ci-crossdock.yml already does it but with v1 components, we can extend it to do v2)
• update documentation website to explain the configuration

[danish9039]

working on it

[pratik-mahalle]

Anyone working on it? or should i take this issue?

[danish9039]

Anyone working on it? or should i take this issue?

Currently working on this