Fix ACE db and setup-job pod security contexts

[ArnobKumarSaha]

Changes

charts/ace/templates/db/db.yaml

• Postgres pod/container security context is no longer OpenShift-only. On OpenShift it keeps using .Values.securityContext.runAsUser; everywhere else runAsUser/runAsGroup/fsGroup are 70 (the postgres uid), via a $dbUser template variable.
• Deduped the repeated resizePolicy block for postgres and pg-coordinator into a $resizePolicy variable.

charts/ace/templates/platform/setup-job.yaml

• Container-level securityContext used nindent 10, which placed its keys at the same indent as the securityContext: key itself — they rendered as sibling container fields and the security context as an empty map. Fixed to nindent 12.
• Set serviceAccount alongside serviceAccountName.

charts/ace/values.yaml

• Added settings.db.resources.requests (500m CPU / 1Gi memory).

Verification

helm template charts/ace -s templates/db/db.yaml renders 70 by default and 65534 with --set global.distro.openshift=true; -s templates/platform/setup-job.yaml now nests the container security context correctly.