Add redis resources + QoS config for Critical sites deployment

Partial https://gitlab.cern.ch/webservices/webframeworks-planning/-/issues/502

Improving redis deployment:

@kosamara continuing our discussion on making redis highly available, we have the following options

1. Deploy redis with sentinel configuration

• According to the documentation, we need atleast 3 sentinel instances (preferable in different az/ nodes) + worker nodes
• Configuration is a bit complex, but we can refer to https://github.com/bitnami/charts/tree/master/bitnami/redis for deployment
• Drupal php clients do support sentinel redis. Ref - https://janaksingh.com/blog/docker-drupal-redis-sentinel/

2. Deploy redis as a cluster

• Although this does provide availability, it doesn't guarantee strong consistency
• Configuration is not very complex, but we can refer to https://github.com/bitnami/charts/tree/master/bitnami/redis-cluster for deployment

added 2 commits

• dcf3d7c6 - Add redis resources
• 167e1c2f - Add envtests for critical sites

Compare with previous version

added 1 commit

• 394d00ce - New changes

Compare with previous version

added 1 commit

• cebb3033 - New changes

Compare with previous version

added 58 commits

• cebb3033...6b073ca8 - 54 commits from branch master
• 8b79d078 - Add replicas, nodeSelector suupport for ciritcal qos
• 114fa04d - Add redis resources
• b90ce9f9 - Add envtests for critical sites
• 10da6e7c - New changes

Compare with previous version

added 1 commit

• ecced532 - Add resources to enable, disable and redis cleanup

Compare with previous version

added 1 commit

• 6bbd097d - Add resources to enable, disable and redis cleanup

Compare with previous version

marked this merge request as ready

requested review from @fborgesa

requested review from @dchatzic