BPDM Chart's initContainers do not have CPU and memory limits specified.
Since they are very basic jobs they should come with a very small CPU and memory footprint.
I don't think it is even necessary to make those limits configurable as I don't see the point of giving a basic delaying container more limit than is absolutely needed.

We should determine the minimum needed and assign it to the deployment file.

Relates to issues like https://github.com/eclipse-tractusx/bpdm/security/code-scanning/4627 and https://github.com/eclipse-tractusx/bpdm/security/code-scanning/4659