Description

As per #12385 we have determined that spanId on the propagationContext is problematic and we want to replace it with other mechanisms.

This is architecturally solved by decoupling the performance part of the SDK from the propagation context. The Propagation context was not designed to feed data to the performance part of the SDK. The propagation context was desinged as part of "tracing without performance". Performance data may feed into the propagation context but not the other way around. When we have non-performance events (ie Errors, Replays, Metrics, whatever), they should first look at current performance context (ie active span) and only as a fallback look at the propagation context. If a span ID is required for a payload and no active span is available, a random span ID should be generated instead.