feat: add more information in spans

[bnjjj]

Related to #911

[netlify]

✅ Deploy Preview for apollo-router-docs canceled.

Name	Link
🔨 Latest commit	1cae323
🔍 Latest deploy log	https://app.netlify.com/sites/apollo-router-docs/deploys/628cab62c8f4980008df7343

[BrynCooke]

Gut feeling is that this information should be in a span in the TowerSubgraphService.
Eventually it is very possible that we will have other types of subgraph service that do not actually make an http call.

[bnjjj]

@BrynCooke Not sure to understand your comment. At the moment I only put these records on the fetch span which is the function to make the http call to the subgraph. It's not on the subgraph_service span right now it's only used on fetch_node method which make the http request.

[BrynCooke]

Yeah, I think the fetch span should stay as it is, and that a new span should go in TowerSubgraphService.
It's TowerSubgraphService that actually does the 'client' work and knows all about http stuff.

Having this client span fetch means that anything in the subgraph service pipeline such as caching would also be marked as client.

I guess the point I'm trying to make is that the existing fetch span is too early to be a client span.