feat: More granular instrumentation and remove long running spans

[NickLarsenNZ]

Description

• [x] Remove long running spans.
  • They are not so useful, and cause trace visualization applications to report the missing parent span for its children.
• [x] Add more granular spans for futures.
• [x] Carry across context between the tls server handling connections, and the axum router endpoints.
  • Without this, two separate traces appear instead of a single trace with a hierarcy of spans from the low level tcp listener up to the route handlers.
• [x] Use fully qualified tracing events and spans (per: https://github.com/stackabletech/decisions/issues/15).
• [x] Update crates (pending: https://github.com/open-telemetry/opentelemetry-rust/issues/1880)

Full chain

[!NOTE] All spans are in the same trace when the client has not sent a trace ID in the request.

Linked traces

When a client sends trace information, we can pick that up and use the trace context from there. Notice the traceparent send is the same one as what is received. The webhook is using the clients trace context from thereon.

[!NOTE] Unfortunately trace ids cannot be updated on spans, so once we are able to extract the trace-id from the headers of a client request, we can only use it from that point forward. But, we are able to add links to spans to make life easier.

Client makes a request, and injects the trace-id into headers. A link appears on the span where the parent context was updated.

Clicking on the link will take you to the trace with the spans that existed before the trace-id was extracted from the headers.

This trace also has a span with a link back to the other.

Similarly in Jaeger

Definition of Done Checklist

• Not all of these items are applicable to all PRs, the author should update this template to only leave the boxes in that are relevant
• Please make sure all these things are done and tick the boxes

# Reviewer
- [x] Code contains useful comments
- [x] Documentation added or updated
- [x] Changelog updated
- [x] Cargo.toml only contains references to git tags (not specific commits or branches)