Request - Refactor configuration of external validation

[leoraba]

Summary of request

Refactor the configuration of external validation endpoint.

Proposed solution: To be able to configure external validation endpoint during category registration (dictionary registration).

Details

Currently, the configuration for external validation is done by setting environment variables (implemented as described in ticket #110), this way of configuring is enough when categoryId and its properties are known, however, when a new category is created, (or a change in configuration is required), it is required to update the env variable with a further application restart to reload the configuration, which make the process difficult when application is already running in production.

Desired solution

Configure external validation endpoint during category registration (dictionary registration), where configuration is stored in the database along with category and dictionary registration.

This could be a solution to handle changes of configuration without application to restart.

[joneubank]

Proposed solution:

By default, make external validation URLs available for all unique properties of every entity from every category.

We should add an environment variable to disable external validation globally.

For future development: we can consider an API that can be used by admin to disable external validation for specific categories or entities. Similarly, admins could enable external validation endpoints for any arbitrary property from a category/entity.