global.image.registry not respected in helm chart for memcache pods

[slim-bean]

          I recently update to the new Helm Chart v6.0 and had a few issues with the memcache portion. These are less major issues and more so quality of life for the chart. For both of these issues the existing chart components already support them, just memcache is the odd one out

1. global.image.registry is not respected by the memcache statefulset.

2. there are no default values for the podSecurityContext for memcache. I ended up going with this for my deployment

podSecurityContext:
    runAsNonRoot: true
    runAsGroup: 1001
    runAsUser: 1001

Originally posted by @Dalktor in #12506 (comment)

[nikable]

Same issue: global.image.registry is not reflecting in memcached pods. Would be nice if someone from the maintainers could possibly confirm this behavior.

Chart version (Helm-Loki): 6.6.5

Existing behavior: global.image.registry is not reflecting in containers from memcached pods. All other pods (except the memcached) generated by this chart are pulling images from the private image registry as configured in "global.image.registry".

Expected behavior: All containers should pull images from the configured private registry as the config should get applied globally.