Queue Integration Tests with Redis Cluster

[vadimonus]

Currently Laravel declares some support for Redis Cluster, but some features are not working (for example, job batches).
This PR adds Queue Integration Tests run with Redis Cluster (on both predis and phpredis). This will allow to check if new and existing features are compatible with Redis Cluster.

Some changes were made to run tests in new environment.

• InteractsWithRedis trait extended, to provide clustered config for redis, if REDIS_CLUSTER_HOSTS_AND_PORTS env variable is passed. This is considered backward compatible change, as currently env with this name is not described anywhere.
• InteractsWithRedis also sets RedisManager instance for application container. Without this change application in tests tries to use application configs leading to behaviour inconsistency (as config in InteractsWithRedis and in application differs). Added cache to config in InteractsWithRedis, to make configs in trait same as in app, and do not break tests, that previously used app configs. This change may be considered backward incompatible. On the other hand, behaviour of InteractsWithRedis is not described anywhere, and is intended to be used only in tests, and this change may be treated as not breaking contracts.
• InteractsWithRedis trait added to RateLimitedWithRedisTest (unlike other tests that interacts with redis, that test missed this trait).
• Redis cluster queue should use {default} queue name instead of queue. RedisQueueTest updated, to take queue name from config. This allow to pass right queue name when tested in cluster.
• testBulkJobQueuedEvent is skipped with redis cluster connection (fix for bulk with cluster and unskipping test will be in separate PR, simular to Job Batches with Redis Cluster #54205)
• redis-cluster example in docker-compose.yml to run local tests with cluster

[github-actions]

Thanks for submitting a PR!

Note that draft PR's are not reviewed. If you would like a review, please mark your pull request as ready for review in the GitHub user interface.

Pull requests that are abandoned in draft may be closed due to inactivity.

[vadimonus]

@taylorotwell returned to draft. Please, clarify, if i should update something