Accept Distributed Trace Headers From New Relic

Is your feature request related to a problem? Please describe.

Our team is utilizing GraphQL-Ruby for a subgraph within an Apollo Federated Supergraph. To achieve comprehensive observability, we're relying on New Relic Distributed Tracing to monitor how requests flow through our various services within the supergraph.

However, we've encountered a roadblock: New Relic tracing currently doesn't accept traceparent or tracestate headers, which limits our ability to achieve the desired level of observability.

Describe the solution you'd like

It would be great if enabling New Relic tracing in GraphQL-Ruby would automatically support distributed tracing, provided it's activated in the project's newrelic.yml configuration file. This feature would streamline our observability efforts without requiring additional effort.

Describe alternatives you've considered

I'm exploring the possibility of extending the GraphQL::Tracing::NewRelicTrace module to add this support. However, this approach is proving to be complex and time-consuming.

Additional context

None

Start by reading the GraphQL::Tracing::NewRelicTrace module and the project's newrelic.yml configuration. Trace how New Relic tracing is enabled and determine where traceparent and tracestate headers would be accepted; done means distributed tracing works when the relevant configuration is enabled, with coverage for that behavior.