Description

This feature request originates from #33912

Currently, the messages from AMQP are coupled to the application. The type header contains the FQCN to the message, so the component can deserialize it back into the correct class.

It is suggested that we allow making the type header more decoupled, by mapping a generic type name to a FQCN in the component. This means messages across 2 different applications don't have to live in the same namespace (or even same language).

Add a "type to FQCN" map to the Messenger component (defaulting to type = FQCN), so messages are decoupled from PHP namespaces. I think this is worth an issue, as some research is needed on how this influences other, non-AMQP, transports (which don't have a content/message type feature)