[BUG] Azure ServiceBus traces are broken in some situations

[stevejgordon]

When the OTel bridge is enabled (the default), and the Azure ServiceBus library is used, we currently see traces where some spans have the incorrect parent ID (parenting themselves). We have identified the root cause: the Azure SDK now emits OTel native instrumentation via the Activity APIs, meaning that our bridge is picking up and instrumenting traces based on two sources. We need to, ideally, ensure that we can handle this scenario without creating invalid spans or at least prevent the OTel bridge from recording additional (repeat) spans for Activities originating from the Azure SDK.

[stevejgordon]

Closed by #2455