Add pod security context templating to CronJob and Job

[alex1989hu]

Is your feature request related to a problem? Please describe.
The current CronJob and Job templates do not provide a way to configure the pod security context. Instead, only the container-level security context is exposed. This limitation prevents users from applying fine-grained security configurations such as setting seccompProfile.

Additionally, the template naming is inconsistent between resources, which can lead to confusion and reduced usability when working across different workload types.

Describe the solution you'd like

• Add support for configuring security context (pod-level and container-level as well) in both CronJob and Job templates, same to what is available in Deployment template.
• Ensure both pod security contexts and container security contexts are configurable and clearly separated.
• Standardize template naming (containerSecurityContext, securityContext) conventions across all workload templates (Deployment, Job, CronJob) for consistency and predictability.

Describe alternatives you've considered
There are no practical alternatives. Pod-level securityContext must be defined directly within the pod template, and currently there is no chart option that enables this configuration for CronJob and Job resources.

Additional context
N/A