SERVER-137201Investigating
Switch from using SDK-provided Spans to using a lightweight implementation
h2. Summary Recording a span for a traced request costs far more than the 10% latency budget in SPM-3868's scope doc allows: on {{crud_bm}} find/insert, tracing every request added about 28%/27% CPU. About half of that was the work of recording the span itself, both in our own span bookkeeping and in the OpenTelemetry C++ SDK's per-span machinery. The other half came from that work's memory and code footprint slowing the rest of the request. This ticket reduces both: # *Part 1, span bookkee