Add Support for Valkey Module Alongside Redis

[GTLOLI]

Hi Pigsty team,

I’d like to suggest adding support for Valkey as an alternative module to Redis.
Since Valkey is a fully open-source fork of Redis (following Redis’s recent license changes), it provides a compatible and community-driven replacement with long-term sustainability and freedom guarantees.

Currently, Pigsty seems to focus primarily on Redis integration. Adding a Valkey module (or an option to deploy Valkey instead of Redis) would:

Offer users a fully open and Apache 2.0–licensed alternative.

Ensure drop-in compatibility for existing Redis workloads.

Future-proof Pigsty deployments against potential Redis license or feature restrictions.

Suggestion:

Provide a valkey module that mirrors the Redis one, using the same configuration structure and orchestration pattern.

Optionally include a toggle (e.g. pigsty_component: redis|valkey) to allow easy switching between the two.

This addition would make Pigsty even more flexible and open-source friendly.

Thanks for your great work on the project!