Dev Task: Redis - include as part of deployment

**Describe the task**
We want a fully deterministic process for deploying and maintaining redis, so we need to create a template and deploy as part of some pipeline.

**Acceptance Criteria**
- [ ] Templates in source control
- [ ] Instructions + script for deploying
- [ ] ??? Part of pipeline? If so - which pipeline? Which product?

**Additional context**
- Redis is used extensively by various process in wps. The current redis deployment configuration being used was manually created in openshift 3.* use the service catalogue. In 4.* the equivalent process would be to use helm developer catalogue to create a deployment.
- We could have multiple applications/projects using redis. e.g. wps-api uses redis, cronjobs, tileservers etc. etc. we need to consider - do we need one redis server? many? do we just have a template that we manually run? do we include it as part of the pipeline?

No repository files or tests are identified. Start by reviewing the existing manually created OpenShift 3.* Redis deployment and the Helm developer catalogue approach for OpenShift 4.*. Resolve whether Redis is shared or per application and which product pipeline owns it; done means source-controlled templates, deployment instructions, a script, and a defined pipeline scope.

Written by the indexing model from the issue text.