feat: add json schema conditional validations

[ishanarya0]

No description provided.

[ishanarya0]

This gives one False Negative, but will ensure that the user can't pass a null value.

A few examples of accepted and not-accepted cases:

ACCEPTED
{
  "host": "http:0.0.0.0:1234",
  "insecure": true,
  "token": "token"
}

NOT ACCEPTED
{
  "host": "http:0.0.0.0:1234",
  "insecure": false,
  "token": "token"
}

ACCEPTED
{
  "host": "http:0.0.0.0:1234",
  "insecure": false,
  "cluster_ca_certificate": "c_ca_cert",
  "token": "token"
}

ACCEPTED
{
  "host": "http:0.0.0.0:1234",
  "cluster_ca_certificate": "c_ca_cert",
  "token": "token"
}

ACCEPTED
{
  "host": "http:0.0.0.0:1234",
  "insecure": true,
  "client_key": "c_key",
  "client_certificate": "c_cert"
}

NOT ACCEPTED
{
  "host": "http:0.0.0.0:1234",
  "insecure": true,
  "client_key": "c_key"
}

NOT ACCEPTED
  "host": "http:0.0.0.0:1234",
  "insecure": true,
  "token": "token",
  "client_key": "c_key",
  "client_certificate": "c_cert"
}

(FALSE NEGATIVE - should be accepted since the token value is present)

ACCEPTED
{
  "host": "http:0.0.0.0:1234",
  "insecure": true,
  "token": "token",
  "client_key": "c_key"
}

(NOTE: it doesn't matter if `client_certificate` is not present, as the token value can be used by entropy)

[rohilsurana]

These test cases are awesome. Can we also write a small test for the json-schema using the test cases mentioned above? This would make sure changes in future can be tested easily as well.

We can do the same for all the other schemas we have in future.

[ishanarya0]

These test cases are awesome. Can we also write a small test for the json-schema using the test cases mentioned above? This would make sure changes in future can be tested easily as well.

We can do the same for all the other schemas we have in future.

Sounds good! I'll add them.