[Messenger] Added transport agnostic exception

[lolmx]

Q	A
Branch?	master
Bug fix?	no
New feature?	yes
BC breaks?	yes
Deprecations?	no
Tests pass?	yes
Fixed tickets	#30346
License	MIT
Doc PR	TODO

As described in #30346, client code shouldn't care about which transport is currently used by the message bus. This pr adds a new generic exception that is thrown by the AmqpSender if the message couldn't be delivered.

[kunicmarko20]

Should it also be added here:

https://github.com/symfony/messenger/blob/0c0e9cfc2fd50a5b6e242204c80855f2f385f9cb/Transport/AmqpExt/AmqpReceiver.php#L70 ?

Didn't check what exception can occur here but I guess it should be consistent.

[lolmx]

I added a catch block whenever the $this->connection->ack($AMQPEnvelope); fails in the receiver, and surrounded $this->connection->reject($AMQPEnvelope); & $this->connection->nack($AMQPEnvelope); because they can fail too.

I did not alter this throw because it's not transport-related.

Although this one is related to transport, I choose to not trow a TransportException because it's an exception manually raised by client code, thus I let client do his stuff :)

[fabpot]

Can you rebase your pull request on current master? You merged master and it makes the PR non-mergeable. thank you.

[lolmx]

My bad, here it is :)

[lolmx]

I checked tests errors, it's Component/Debug and Bundle/FrameworkBundle, which are failing on upstream/master too

[fabpot]

Thank you @lolmx.