Installer subchart renders empty initContainers block when no initContainers are present

[rbogendoerfer]

Describe the bug
The installer subchart renders an empty initContainers block in the job when no initContainers are defined:

      initContainers:
      containers:
      - name: pega-installer
        image: pega-docker.downloads.pega.com/platform/installer:25.1.1

This empty block confuses some conformity scanners and causes conformity checks to fail.

To Reproduce
Use out-of-the-box charts 4.2.0 with global.actions.execute=install and don't define any initContainers, etc. The rendered template will have the empty initContainers tag.

Expected behavior
When no initContainers are defined there should not be an initContainers block at all.

Chart version
4.2.0 without customizations

Server (if applicable, please complete the following information):
n/a

Additional context
n/a

[misterdorito]

While there was a recent change (in 4.2.0) to allow custom initContainer definitions for installer/upgrade jobs, this would have been the case for quite some time (definitely not a new thing).

[rbogendoerfer]

@misterdorito I guess you are right, this is not a new issue and probably has been part of the manifest for a longer time.
Reason this just showed up right now is that this empty initContainers block confuses the security/conformity scanner of a new client, who basically raised this issue to me.