fix: adjust values.schema.json to support client credentials in config or envs [PC-12120]

[mkaras-nobl9]

Summary

• valid value files are:

  deployment:
    extraEnvs:
     - name: N9_CLIENT_ID
       valueFrom:
         secretKeyRef:
           key: client_id
           name: my-existing-secret
     - name: N9_CLIENT_SECRET
       valueFrom:
         secretKeyRef:
           key: client_secret
           name: my-existing-secret
  

  or

  config:
    clientId: "theClientId"
    clientSecret: "theClientSecret"
  

• when env and config are missing, validation expects config values to be present

Error: INSTALLATION FAILED: values don't meet the specifications of the schema(s) in the following chart(s):
nobl9-agent:
- (root): Must validate "else" as "if" was not valid
- config.clientSecret: Invalid type. Expected: string, given: null
- (root): Must validate "else" as "if" was not valid
- config.clientId: Invalid type. Expected: string, given: null
- (root): Must validate all the schemas (allOf)

• when both env and config are passed, it expects config values to be null

Error: INSTALLATION FAILED: values don't meet the specifications of the schema(s) in the following chart(s):
nobl9-agent:
- (root): Must validate "then" as "if" was valid
- config.clientSecret: Invalid type. Expected: null, given: string
- (root): Must validate "then" as "if" was valid
- config.clientId: Invalid type. Expected: null, given: string
- (root): Must validate all the schemas (allOf)

[triluch]

This still has "object" types where there are arrays - extraVolumeMounts for example.
Please also test extraEnvs with other possible combinations - for example fieldRef or configMap sources.