This PR was squashed before being merged into the 7.2 branch.Discussion----------[Messenger] Document `getRetryDelay()`Documentation for code [57915](symfony/symfony#57915)Commits-------646e199 [Messenger] Document `getRetryDelay()`

…xceptionInterface` (AydinHassan)This PR was merged into the 7.2 branch.Discussion----------[Messenger ] Extract retry delay from nested `RecoverableExceptionInterface`| Q             | A| ------------- | ---| Branch?       | 7.2| Bug fix?      | yes| New feature?  | no| Deprecations? | no| Issues        | n/a| License       | MITHey,In#57915 the ability to add a retry delay to `RecoverableExceptionInterface` was implemented. However, I noticed while debugging that it in my case the custom delay was not being applied because `RecoverableExceptionInterface` is wrapped in a `HandlerFailedException` in:https://github.com/symfony/symfony/blob/7a16efefdee2d282cd6ccfd6ecb0b82ff5a06936/src/Symfony/Component/Messenger/Middleware/HandleMessageMiddleware.php#L124For detecting whether we should retry we already unwrap `HandlerFailedException` so I implemented a similar method to fetch the delay, simply getting it from the first `RecoverableExceptionInterface`.Maybe we need something more advanced, so your feedback there would be appreciated!Commits-------4a02222 [Messenger ] Extract retry delay from nested `RecoverableExceptionInterface`