…essage publishing (G15N, sroze)This PR was merged into the 4.3-dev branch.Discussion----------[messenger] Adds a stamp to provide a routing key on message publishing| Q             | A| ------------- | ---| Branch?       | master| Bug fix?      | no| New feature?  | yes| BC breaks?    | no| Deprecations? | no| Tests pass?   | yes| Fixed tickets |#29950| License       | MIT| Doc PR        |symfony/symfony-docs#11236Adds a stamp allowing to set a `routing_key` at `MessageBus::dispatch()` level.```php$message = (new Envelope('message'))->with(new RoutingKeyStamp('routing_key'));$bus->dispatch($message);```Commits-------a515635 Simply code and rename "configuration" to "options"3151b54 [messenger] AMQP configurable routing key & multiple queues

…transport (sroze)This PR was merged into the 4.3-dev branch.Discussion----------[Messenger] Allows to register handlers on a specific transport| Q             | A| ------------- | ---| Branch?       | master| Bug fix?      | no| New feature?  | yes| BC breaks?    | no| Deprecations? | no| Tests pass?   | yes| Fixed tickets |#30110| License       | MIT| Doc PR        |symfony/symfony-docs#11236With the#30008 pull-request in, we can now do the following:```yamlframework:    messenger:        transports:            events:                dsn: amqp://guest:guest@127.0.0.1/%2f/events                options:                    queues:                        3rdparty:                            binding_keys: [ 3rdparty ]                        projection:                            binding_keys: [ projection ]            events_3rdparty: amqp://guest:guest@127.0.0.1/%2f/events?queues[3rdparty]            events_projection: amqp://guest:guest@127.0.0.1/%2f/events?queues[projection]        routing:            'App\Message\RegisterBet': events```This will bind two queues to the `events` exchange, fantastic:<img width="325" alt="Screenshot 2019-04-07 at 10 26 27" src="https://user-images.githubusercontent.com/804625/55680861-af373580-591f-11e9-8f1e-2d3b6ddba2fd.png">---Now, in this setup, the message will be duplicated within the `3rdparty` & `projection` queues. If you just run the consumer for each transport, it will consume the message and call all the handlers. You can't do different things based on which queue you have consumed the message. **This pull-request adds the following feature:**```phpclass RegisterBetHandler implements MessageSubscriberInterface{    public function __invoke(RegisterBet $message)    {        // Do something only when the message comes from the `events_projection` transport...    }    /**     * {@inheritdoc}     */    public static function getHandledMessages(): iterable    {        yield RegisterBet::class => [            'from_transport' => 'events_projection',        ];    }}```---In the debugger, it looks like this:<img width="649" alt="Screenshot 2019-04-07 at 10 29 55" src="https://user-images.githubusercontent.com/804625/55680892-1d7bf800-5920-11e9-80f7-853f0201c6d8.png">Commits-------f0b2acd Allows to register handlers on a specific transport (and get rid of this handler alias)