Authservice Redis wait initContainer renders invalid securityContext when Redis `containerSecurityContext.enabled` is set
**Description**
Enabling Authservice with Redis can render an invalid Deployment because the Authservice chart copies Redis chart values directly into the `wait-for-redis` initContainer `securityContext`.
The issue was exposed while testing Jaeger with ambient overrides, but the root cause is in the Authservice chart.
**Reproduction Chain**
1. Jaeger ambient override enables Authservice:
```yaml
addons:
authservice:
enabled: true
```
2. Big Bang test values enable Authservice Redis:
```yaml
redis:
enabled: true
```
3. Authservice renders a `wait-for-redis` initContainer when Redis is enabled.
4. The Deployment template copies this Redis value directly:
```gotemplate
securityContext:
{{- toYaml (index .Values "redis-bb" "upstream" "master" "containerSecurityContext") | nindent 12 }}
```
5. Redis chart values may include:
```yaml
containerSecurityContext:
enabled: true
runAsUser: 1001
```
`enabled` is valid as a Redis chart values key, but it is not a valid Kubernetes `container.securityContext` field. Kubernetes rejects the rendered Deployment.
**Expected Behavior**
Authservice should render a valid Kubernetes `securityContext` for the `wait-for-redis` initContainer when Redis is enabled.
**Actual Behavior**
The rendered initContainer can include:
```yaml
securityContext:
enabled: true
runAsUser: 1001
```
This is rejected by Kubernetes because `enabled` is not part of the Pod/Container `securityContext` API.
issue