[chore]: propagate jaeger-query health to collector runtime

[aaryan359]

Requirement

Summary

The jaeger-query extension currently starts its HTTP and gRPC servers but does not propagate health status changes to the OpenTelemetry Collector runtime. As a result, the collector reports the extension as healthy even when the query server fails or shuts down.

This chore implements the missing health status propagation so that the collector’s view of system health accurately reflects the runtime state of the query service.

---

What needs to be done

• Propagate jaeger-query server health changes to the collector runtime
• Report StatusOK when the query server starts successfully
• Report StatusFatalError when the HTTP or gRPC server fails at runtime
• Report an appropriate status on shutdown
• Use the existing componentstatus and telemetry.Settings.ReportStatus mechanisms
• Remove the existing TODO related to health propagation once implemented

---

Why this is needed

• Improves observability and operational correctness
• Ensures collector health endpoints and monitoring reflect the true state of the query service
• Aligns jaeger-query with other Jaeger extensions that already report component health
• Does not change data ingestion or query behavior; this is observability-only

---

Scope / Notes

• No user-facing API or configuration changes
• No impact on trace ingestion or storage
• Backward compatible
• Implementation follows established OpenTelemetry Collector patterns

[aaryan359]

@yurishkuro, @jkowall, I found this TODO in the code, and I solved it. Can you review this?

[mehrdadbn9]

I can fix the health status propagation between components. Plan: Implement health check aggregation and proper status forwarding in the health check handler. If maintainer thinks this needs fixing, please assign to me.