feat(gatsby-source-drupal): Add tracing for full/delta fetches and http requests

[KyleAMathews]

Trace the key parts of the gatsby-source-drupal lifecycle.

Full fetch:

Delta fetch (fastbuilds):

I've been working out a schema we can use across source plugins. The idea being that each source plugin is semantically similar so if we use span names then we can directly compare source plugins to each other.

Rules:

• all span names in plugins are prefixed by the lifecycle method e.g. sourceNodes.fetch
• set the plugin name as a tag on each span
• source nodes fetch, touch nodes (if the fetch is delta), and create nodes. Name these spans sourceNodes.fetch, sourceNodes.touchNodes, and sourceNodes.createNodes
  • for fetch, set as tag if the fetch is full or delta
  • for touchNoes, set the count for how many nodes are touched
  • for createNodes, set if the fetch is delta or full & the count

[KyleAMathews]

plugin spans were being set as children of the run-api span instead of the run-plugin span — this fixes that

[KyleAMathews]

touchNodes seems to start taking an inordinate amount of time as the node count grows. So let's track it.

[KyleAMathews]

tag names taken from https://github.com/open-telemetry/opentelemetry-js/tree/main/packages/opentelemetry-instrumentation-http

[benrobertsonio]

looks good to me :)