Support for valkey-py based client manager

[Ohnoimded]

Problem

Since Redis has been forked to Valkey and many projects are likely to adopt Valkey over Redis, using RedisManager/AsyncRedisManager no longer works with Valkey URLs (e.g., valkey://...) and valkey-py, as it only checks for Redis URLs (e.g., redis://...).

Solution

I created a custom implementation called ValkeyManager/AsyncValkeyManager inherited from PubSubManager/AsyncPubSubManager, using valkey-py instead of redis-py.

Why This Matters

Due to Redis' licensing change, many projects are transitioning to Valkey. Adding support for Valkey URLs would help users migrate seamlessly and avoid the need for custom solutions.

Request

Would it be possible to integrate support for Valkey URLs in the official implementation? This would make it easier for projects to adopt Valkey.

[miguelgrinberg]

Instead of duplicating the existing classes that work with Redis, I would prefer to extend them to support either the Redis or the Valkey clients. This would avoid code duplication, at least while the two projects mantain similar APIs.

[Ohnoimded]

Sounds like a good idea. Can I make a PR for this?

[miguelgrinberg]

@Ohnoimded Sure, go ahead and submit a PR once done.