Feature Request: Valkey clusters support

Expected Behavior
Add support for valkey connections (same as with a redis cluster).

Current Behavior
Specific support for valkey not available.

Context
Since Redis has changed the way licensing works, the major Cloud providers (AWS, Google, etc.) are switching to the Valkey project (https://valkey.io/). This project is a fork of Redis, but is set to depart from that.
Here is a discussion on the valkey project https://github.com/orgs/valkey-io/discussions/1876 that might be of help.

How has this issue affected you?
Right now we are using AWS Elasticache for Redis, but since the licensing change in Redis, no updates are expected beyond Redis 7.1. Additionally, since Valkey is implementing several optimizations thought for cloud environments, it has a lower cost than Redis clusters.

What are you trying to accomplish?
We want (in the future) to migrate from Redis to a Valkey cluster and continue to use spring sessions. Also, we will benefit from the vast improvements done.

What other alternatives have you considered?
Right now, we are staying with a Redis cluster in 7.1. If they drop support for that version, we will need to find a way to mount our own Redis or something.

Are you aware of any workarounds?
The only option would be to mount our own Redis cluster and maintain it.

The issue does not name specific files or tests. Start by examining the existing Redis cluster support in Spring Session and determine where connection handling and compatibility are implemented. Done means Spring Session can connect to and operate with Valkey clusters, with coverage for the supported cluster behavior.