Missing b3 trace information in gql server logs

### Version Information

Server Version: v2.4.0
CLI Version (for CLI related issue): v2.4.0

### Environment

`./server`

### What is the expected behaviour?

When passing tracing headers, X-B3-*, expecting the server to output tracing data to a Zipkin endpoint.

### Keywords

tracing, b3, zipkin, opentelemetry

### What is the current behaviour?

There's no way to extract the tracing information.

### How to reproduce the issue?

1. Start v2.4.0
2. `curl -H "X-Hasura-Admin-Secret: EXAMPLE" -H "X-B3-TraceId: 463ac35c9f6413ad48485a3953bb6124" -X "X-B3-SpanId: a2fb4a1d1a96d312" "X-B3-Parent-SpanId: a2fb4a1d1a96d312" -X POST http://localhost:8080/v1/graphql -d '{"query":"query MyQuery {\n apps {\n id\n }\n}\n","variables":null,"operationName":"MyQuery"}'` — or some other query that is available to your environment

Now you'd expect to at least see the headers in the logs of the server, or even better to have them shipped.

### Please provide any traces or logs that could help here.

I'd love to provide some traces here.

### Can you identify the location in the source code where the problem exists?

No

### If the bug is confirmed, would you be willing to submit a PR?

No

Start by reproducing the request against ./server at /v1/graphql with the supplied X-B3-* headers, then inspect the server logs and existing tracing behavior. The issue is complete when the request's tracing information is available in server logs or is shipped to a Zipkin endpoint.

Written by the indexing model from the issue text.