[RedisMessengerBridge] Add a delete_after_ack option

[Seldaek]

This allows Messenger to clean up processed messages from memory, avoiding a mem "leak" in redis

Q	A
Branch?	master
Bug fix?	no
New feature?	yes
Deprecations?	no
Tickets	#33715
License	MIT
Doc PR	symfony/symfony-docs#... TODO - will pile it on to symfony/symfony-docs#11869 as it kinda binds together and a bigger refactor of the docs here is much needed to avoid all these gotchas

Right now by default a redis transport for messenger will leak memory as all messages stay in redis forever. You can configure stream_max_entries to automatically trim to a max of X entries, but that means if you have big peaks in messages you might start losing messages which have not been processed.

This PR provides an alternative to that, by deleting message as they are processed. This is ideal as it avoids having to find the right number for stream_max_entries (do you want to risk losing data or use more memory than needed on average?). The only catch is that if you have multiple groups consuming the same stream, the first one processing a message will delete it, so other groups will not see it. For that reason setup() attempts to detect this and fails hard if it is misconfigured to prevent data loss.

[chalasr]

Should be enough to close #33715.

[fabpot]

LGTM to tests are broken.

[Seldaek]

Fixed tests now, seems the failing ones are unrelated.

[fabpot]

Thank you @Seldaek.

[plfort]

Does this feature can be backported on 4.4 ?

[stloyd]

@plfort New feature are never backported into already released versions, backported are only bugfixes.