add configuration for trace_id

[bnjjj]

close #2080

Configuration example:

telemetry:
  tracing:
    experimental_response_trace_id:
      enabled: true # default: false
      header_name: "my-trace-id" # default: "apollo-trace-id"
    propagation:
      request: 
        header_name: "x-request-id"
      jaeger: true

TODO:

• Tests
• Enable it in dev mode
• docs

[abernix]

Couple small comments!

[BrynCooke]

Approved with the following comments.

1. Not sure we should at this stage bother populating the response headers in the ApolloExporter. It's potentially inaccurate right now, and we'll need to think about how we configure this properly.

2. Still not keen on the enabled thing. Would prefer that the value "default" is used under the header_name. There's no hard and fast rules on when to use enabled, but I guess we can tackle this when we move out of experimental.

[garypen]

Looks great. One question that I'd like to know the answer to.

[o0Ignition0o]

LGTM overall, a couple of nits that seem to be copy paste mishaps.

Love the experimental documentation section, this is great! ❤️

[bnjjj]

@BrynCooke

Approved with the following comments.

1. Not sure we should at this stage bother populating the response headers in the ApolloExporter. It's potentially inaccurate right now, and we'll need to think about how we configure this properly.

We agreed with the studio team to use this as a workaround right now, they have an issue on their side to add a field in proto file to handle that correctly. It's still correct except we don't insert all response headers inside. We discussed with Jesse about that and if we see a need or request from our users we will add them all later but for now that's ok.

2. Still not keen on the enabled thing. Would prefer that the value "default" is used under the header_name. There's no hard and fast rules on when to use enabled, but I guess we can tackle this when we move out of experimental.

Could you add this comment in the right discussion please ? --> #2147