SS 1233 Kubernetes manifest yaml validation

[alfredeen]

Description

This PR adds k8s manifest validation when creating or re-deploying new k8s deployments. The validation is run in development environments (DEBUG mode). The validation uses kubernetes-validate to validate the deployment yaml and also performs a light validation of the custom kubernetes-pod-patches section if it exists in a ConfigMap.

If the manifest is determined to be invalid, then the values and deployment yaml files are saved to the charts/values directory for further investigation. In that case 2 files are saved:

A values file: [date]_[uuid].yaml
A deployment file: [date]_[uuid]_deployment.yaml

Jira link

Checklist

• This pull request is against develop branch (not applicable for hotfixes)
• I have included a link to the issue on GitHub or JIRA (if any)
• I have included migration files (if there are changes to the model classes)
• I have included, reviewed and executed tests (unit and end2end) to complement my changes
• I have updated the related documentation (if necessary)
• I have added a reviewer for this pull request
• I have added myself as an author for this pull request
• In the case I have modified settings.py, then I have also updated the studio-settings-configmap.yaml file in serve-charts