Add option to values.yaml to specify a securityContext

Some pods may need a different than default security context (see https://kubernetes.io/docs/tasks/configure-pod-container/security-context/) this issue will implement a way to specify the security context in a micro service cloudharness `values.yaml` file

Locate the relevant microservice values.yaml and the templates that consume pod settings; start by comparing current defaults with Kubernetes securityContext documentation. Done means a service can specify a non-default security context through values.yaml and the rendered pod receives it.

Written by the indexing model from the issue text.