Baggage header not automatically propagating in traces for Pubsub APIs

In what area(s)?

/area runtime

What version of Dapr?

1.18.2

Expected Behavior

Baggage header in Dapr tracing doesn't automatically propagate today automatically for the Pubsub APIs.

Actual Behavior

It needs to be manually propagated via the publisher code. It works for http and service invocation but fails on pubsub (grpc) and potentially workflow APIs.

Release Note

RELEASE NOTE: FIX Baggage header automatically propagates now in pubsub traces