Release v1.56.2

🛠️Fixes

Consumer spans are now real children of the producer's trace across all Pub/Sub backends — Kafka, NATS, Google Pub/Sub, and SQS — while still preserving the existing OTel span link for fan-out semantics.

Previously, each consumer span started from a fresh root context, so an end-to-end publish/subscribe flow appeared as multiple disconnected traces in Jaeger, Tempo, andtracer.gofr.dev. Now the consumer span inherits the producer's trace ID and parent, giving you a single connected trace across all services with no extra configuration.

• Fan-out preserved — span link is still attached for tools that surface fan-out semantics
• Applies to: Kafka, NATS, Google Pub/Sub, SQS