On Kubernetes environments with strict securityContext policies, the builder and demomode pods cannot start

### Describe the bug

On Kubernetes environments with strict securityContext policies, the builder and demomode pods cannot start. Currently, the builder is taking the specs from the builder yaml from configuration, but it does not take also the container specs, where some securityContext policies are defined. Also the demomode pod takes the specs from the deployment.jkube.yaml, but only partially, leaving out the securityContext.

More information inside the discussion item: https://github.com/apache/camel-karavan/discussions/1364

### Steps to reproduce the behavior

1. Add securityContext elements to the builder and demomode pods
2. Run them, and check the yaml of the k8s files
3. The securityContext is not taken from the configuration

### Variant

Web Application

### Container Management (if applicable)

Kubernetes

### Operating System (if applicable)

None

### Version

4.8.0

### Relevant log output

_No response_

Read the discussion in #1364 and compare the builder YAML from configuration with the generated builder pod, then inspect deployment.jkube.yaml and the generated demomode pod. Reproduce the strict-securityContext setup from the issue and verify that the configured container securityContext appears in both generated Kubernetes resources.

Written by the indexing model from the issue text.