fix: podSecurityContext for frontend

[fernandezcuesta]

Add the ability to customize the podSecurityContext for the frontend pod.
Also, add the missing API and Kind for the PVC, which triggers diffs on ArgoCD.

[Copilot]

Pull Request Overview

This PR fixes the missing pod security context for the frontend pod and updates the PVC configuration in the API server StatefulSet to include the required apiVersion and kind fields.

• Enable customization of the pod security context for the frontend pod
• Update the values schema and deployment template with podSecurityContext settings
• Add missing apiVersion and kind fields to the PVC volumeClaimTemplates for the API server to resolve ArgoCD diffs

Reviewed Changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated no comments.

File	Description
charts/dependency-track/values.yaml	Added podSecurityContext settings for the frontend pod
charts/dependency-track/values.schema.json	Included podSecurityContext property in the schema
charts/dependency-track/templates/frontend/deployment.yaml	Updated deployment to conditionally add the pod security context
charts/dependency-track/templates/api-server/statefulset.yaml	Added missing apiVersion and kind fields for the PVC volumeClaimTemplates

Comments suppressed due to low confidence (2)

charts/dependency-track/templates/frontend/deployment.yaml:31

• Consider aligning the key name in the rendered output with the values file (i.e., using 'podSecurityContext') for clarity, as 'securityContext' may be confused with container-level security settings.

      {{- with .Values.frontend.podSecurityContext }}

charts/dependency-track/templates/api-server/statefulset.yaml:133

• Ensure the new 'apiVersion' and 'kind' fields in the volumeClaimTemplates adhere to the expected schema and consider adding documentation if this change impacts downstream processes like ArgoCD integrations.

    kind: PersistentVolumeClaim