[BUG] Tracing: we should strip correation-context/and/or baggage when calling Azure services

[lmolkova]

Library name and version

Azure.Core

Describe the bug

Activity.Baggage is propagated by default via Correlation-Context and can be too big:

• It can affect perf by increasing header size
• it can reach service header size limits

HttpClient propagates Correlation-Context (by default) as long as it's set on the activity.

Expected behavior

Correlation-Context is user app concern and should not be passed to Azure services.

We can set all baggage items to null using Activity.SetBaggage. If it's proven to be unreliable/not performant, we should work with .NET to turn off baggage propagation (to specific endpoints) in BCL.

Actual behavior

If users add things into their activity.Baggage, we propagate them along with our activities

Reproduction Steps

TBD

Environment

No response

[kirankumarkolli]

Thanks you @lmolkova for creating the issue.
One of ComsosDB CX has a livesite incident due to this. Cosmos service has header size limitations of 20KB and context overshoot that, resulting in BadRequests.