Connect: allow specifying resources in templates

Motivation: AKS has some azure-policies in place which deny spawning pods without a resource definition. This applies to the packrat-restore pods and eventually denies app deployment.

values.yml:

  templateValues:
    service:
      type: ClusterIP
      annotations: {}
      labels: {}
    pod:
      annotations: {}
      labels: {}
      serviceAccountName: ""
      volumes: []
      volumeMounts: []
      imagePullPolicy: ""
      imagePullSecrets: []
      initContainers: []
      extraContainers: []
      resources: {} # <---- NEW

As a workaround I am currently trying with

launcher:
  enabled: true
  useTemplates: false
  launcherKubernetesProfilesConf:
    "*":
      job-json-overrides:
        - name: resources
          target: /spec/template/spec/containers/resources
          json:
            requests:
              cpu: "100m"
              memory: "200Mi"
              ephemeral-storage: "200Mi"
            limits:
              cpu: "1000m"
              memory: "1Gi"
              ephemeral-storage: "2Gi"

but this specification results in a 500 from the launcher.

EDIT:

I see the values are just passed along as is and are not limited by the values.yml specification.

So the following

launcher:
  enabled: true
  useTemplates: false
  templateValues:
    pod:
      resources:

works!

Start with values.yml and the templateValues.pod configuration, then trace how those values are passed into the launcher templates. Verify with a rendered deployment that resource requests and limits reach the packrat-restore and other generated pods, and check whether existing chart validation or documentation reflects the supported setting.