"privileged: true" in pod spec clobbers SELinux options

**Image I'm using:**
`aws-k8s-1.28`

**What I expected to happen:**
I ran a pod with this security context:
```
securityContext:
privileged: true
seLinuxOptions:
type: super_t
```

I expected the pod's process to have the `super_t` label on the running system.

**What actually happened:**
The pod's process had the `control_t` label instead.

**How to reproduce the problem:**
See above.