Introduce capability to externalize JSON data validation

[rameshmalla]

Is your feature request related to a problem? Please describe.

Currently, the custom resource expects the JSON schema to be present along with the data, and this JSON schema is used by the operator to validate the data. While this approach functions as intended, there are a few limitations:

• If the data is too large, the corresponding JSON schema will likely increase in size, consequently expanding the size of the custom resource.
• There are scenarios where more robust validations on the data might be necessary, which may not be adequately covered by the JSON schema.

Describe the solution you'd like

The proposl is to allow users to externalize data validations to a service (or lambda) and exposing it via a REST API, which can then be utilized by the config-operator for data validation before creating the config-map. This approach has several advantages over embedding the JSON schema directly in the custom resource:

• Reduced Custom Resource Size
• Dynamic and Extensible Validations