bug #12209 [Messenger] Use new TransportInterface (OskarStark)

This PR was merged into the 4.3 branch.

Discussion
----------

[Messenger] Use new TransportInterface

Fixes #11972

<!--

If your pull request fixes a BUG, use the oldest maintained branch that contains
the bug (see https://symfony.com/roadmap for the list of maintained branches).

If your pull request documents a NEW FEATURE, use the same Symfony branch where
the feature was introduced (and `master` for features of unreleased versions).

-->

Commits
-------

2f61ef2 [Messenger] Use new TransportInterface

Author: OskarStark

messenger/custom-transport.rst

@@ -28,22 +28,31 @@ DSN. You will need a transport factory::
         }
     }
 
-The transport object needs to implement the ``TransportInterface`` (which simply combines
-the ``SenderInterface`` and ``ReceiverInterface``). It will look like this::
+The transport object needs to implement the
+:class:`Symfony\\Component\\Messenger\\Transport\\TransportInterface`
+(which combines the :class:`Symfony\\Component\\Messenger\\Transport\\Sender\\SenderInterface`
+and :class:`Symfony\\Component\\Messenger\\Transport\\Receiver\\ReceiverInterface`)::
+
+    use Symfony\Component\Messenger\Envelope;
 
     class YourTransport implements TransportInterface
     {
-        public function send(Envelope $envelope): Envelope
+        public function get(): iterable
         {
             // ...
         }
 
-        public function receive(callable $handler): void
+        public function ack(Envelope $envelope): void
         {
             // ...
         }
 
-        public function stop(): void
+        public function reject(Envelope $envelope): void
+        {
+            // ...
+        }
+
+        public function send(Envelope $envelope): Envelope
         {
             // ...
         }