Support for valkey instead of Redis

[matvp91]

Is your feature request related to a problem? Please describe.
The job orchestrator relies on BullMQ, which is tightly coupled with Redis. With the latest Redis debacle, we might take a look if we can move to valkey (https://github.com/valkey-io/valkey) entirely.

Describe the solution you'd like
Investigate if valkey is feasable.

Additional context
BullMQ seems compatible, see taskforcesh/bullmq#2642 and https://x.com/manast/status/1841042438510494090, thus API and Artisan shall be compatible too.

For Stitcher, we can add a new adapter and rely on env variables specifically for valkey. Or we can re-use REDIS_HOST and REDIS_PORT but use a different KV store underneath.

[volyx]

Thank you for this awesome project! I was wondering if a Postgres table could be used as a queue instead of Redis/valkey. I've heard that Postgres is often used in this way (for example, here's a random link from the internet: https://news.ycombinator.com/item?id=39315833).

[matvp91]

BullMQ is heavily integrated in Superstreamer to orchestrate the queue / workers, moving to Postgres would have us drop BullMQ and write our own scheduler. Not quiet sure I see a benefit in that.

Nonetheless, Postgres is great though!