Add Symfony Messenger Tracing Support to sentry

[hackzilla]

Problem Statement

As a developer leveraging Symfony Messenger alongside Sentry, I’ve found it difficult to gain visibility into background queue execution. While exceptions are captured correctly, there is currently no automatic tracing support for Messenger messages. When exceptions are captured, they are missing any information about called them, other than command messenger:consume.

This leads to a major observability blind spot in our application:
• We cannot correlate background jobs with the originating request or trace.
• There’s no visibility into queue performance or message processing time.
• Breadcrumbs must be manually added to capture any context (e.g., message class, receiver name).
• The Sentry UI (e.g., the Queues Dashboard) shows no data for PHP applications using Symfony Messenger.

This limits our ability to diagnose latency, track down message-related failures, or analyze system bottlenecks across our infrastructure.

Solution Brainstorm

Add automatic hooks for messenger, like Laravel, for messenger.
https://docs.sentry.io/platforms/php/tracing/instrumentation/queues-module/

[cleptric]

This could be implemented as a middleware, that would start a new transaction for each meassage. TBD about how we can instrument the producing side and how to handle sync consumers.
In Laravel, we can simply listen to events, I haven't checked the internals for Symfony yet.