Kibana init container `elastic-internal-init` has no security context set. I think it's because of an oversight [here](https://github.com/elastic/cloud-on-k8s/pull/8389#discussion_r2352194461). We should also adjust the unit test `TestNewInitContainer` in which `tt.args.setDefaultSecurityContext` is actually not used.