Introduce Valkey image

[lbajsarowicz]

Magento 2.4.8 requires valkey/valkey:8.0
Let's introduce that to the list of supported images.

[navarr]

Supports, not requires but yes! Should make this a priority.

[lbajsarowicz]

Oh, I haven't verified whether Redis is still supported.
Official document states that only Valkey 8 is supported:

[navarr]

Oh! That may be my confusion then, the change log only said

This release includes support for Valkey 8.x.

So I'm guessing they still support Redis but they really really want you on Valkey

[navarr]

@lbajsarowicz Watch #860 for more info

[navarr]

Valkey images now exist; though there is no way to automatically use them yet.

[bap14]

@navarr There should really be a discussion on adding third-party services like this and if building our own without adding anything is the correct approach. It's really a question of "why are we building _____ image?" when the dockerfile is 2 lines (it's not just this service). I don't have an issue, but just wonder if this is the correct, and maintainable, approach.

I generally would prefer to only build what we need to build, and leave those that are just "namespace changes" as "native" third party images.

[navarr]

I would vastly prefer to just leave them as third party images. What we're doing at this point is essentially proxying or backing them up so that - god forbid one of them disappears - we still have it. It also means that if we decide to make a config change or add something to an image, we don't have to update Warden itself to do it.

I know we're also pretty inconsistent about this, there are definitely some images we don't proxy in this fashion.