chore: Repair dev dependency Valkey

What does this MR do?

• This rips out the helm installation in favor of kustomize object injection for development dependencies
• With the recent change from bitnami, all dependencies will fail, images have moved, which is the greater change preventing dev deps from working properly in a development environment
• We don't need that heavy lifting when in test mode, operators, license, helm charts, and similar
• This removes the helm deployment and instead relies on directly created kubernetes manifests.
• This is simple, clean, and easily can be bashed and recreated when/if necessary

If this solution is found to be acceptable, we can transition all other dependencies as well.

I'm starting with valkey as it's relatively simple, and is a great Proof of Concept for the desired outcome.

Author's Checklist

For anything in this list which will not be completed, please provide a reason in the MR discussion.

Required

• Ensure a release milestone is set.
• MR title and description are up to date, accurate, and descriptive.
• MR targeting the appropriate branch.
• MR has a green pipeline on GitLab.com.
• When ready for review, MR is labeled workflowready for review per the MR workflow.

Expected

• Test plan indicating conditions for success has been posted and passes.
• Documentation is created or updated.
• Tests are added.

Related issues

#204