Baggage namespace has conflict with `CoreBaggage.Baggage`

[apple]

Baggage namespace has conflict with `CoreBaggage.Baggage`

[Lukasa]

+1 for BaggageModule.

[slashmo]

+1 on BaggageModule too.

[ktoso]

Paging @tomerd @weissi @Lukasa to discuss this one...

Originally when we prepared the packages we intentionally made the packages CoreBaggage which contains Baggage and Baggage which contains LoggingContext. It was deemed fine at the time, but seems we have an issue.

The baggage type will remain even with task local values present I think, although as usual it is "very hidden" and noone should need to touch it except a few tracer implementations.

So this is more about the LoggingContext being a name which may need disambiguation... though I'd argue others should not define their own LoggingContext and could call them MyFrameworkLoggingContext, which again solves the issue then.

I think we're also working to improve the namespacing issues if I remember correctly @tomerd ?

[ktoso]

We could do BaggageModule I guess similar to what stdlib team projects do https://github.com/apple/swift-collections/tree/main/Sources

[ktoso]

Sounds good -- could you send in a PR @fabianfett ? I'll tag a release then and update the dependency in the main tracing repo so noone should really notice the change in practice.

Thanks for noticing!

[slashmo]

Closed via #13, the module name is now InstrumentationBaggage.