[Messenger] Added the ability to force RedisCluster

[adideas]

Q	A
Branch?	7.1
Bug fix?	no
New feature?	yes
Deprecations?	no
Issues	Fix #...
License	MIT

Previously, an array had to be specified to support a cluster. But the nodes can change. Instead of "redis://host-0,redis://host-1" we specify "redis://server?redis_cluster=true"

[carsonbot]

Hey!

I see that this is your first PR. That is great! Welcome!

Symfony has a contribution guide which I suggest you to read.

In short:

• Always add tests
• Keep backward compatibility (see https://symfony.com/bc).
• Bug fixes must be submitted against the lowest maintained branch where they apply (see https://symfony.com/releases)
• Features and deprecations must be submitted against the 7.1 branch.

Review the GitHub status checks of your pull request and try to solve the reported issues. If some tests are failing, try to see if they are failing because of this change.

When two Symfony core team members approve this change, it will be merged and you will become an official Symfony contributor!
If this PR is merged in a lower version branch, it will be merged up to all maintained branches within a few days.

I am going to sit back now and wait for the reviews.

Cheers!

Carsonbot

[valtzu]

I like it.

Any reason to call the parameter redis_cluster instead of just cluster?

EDIT: ok I guess it's kinda in line with redis_sentinel

[adideas]

If you specify a cluster but do not specify it as an array, then a regular redis will start. Then the cluster reports MOVED and everything breaks down.

In the log you can see an error that is most incomprehensible "MOVED ...". You start looking in the documentation and find the redis_cluster parameter in the cache. And then you think why it’s not in "Messenger"

[adideas]

Tell me, did you fix the tests?