Make configuration solver dependent

**Is your feature request related to a problem? Please describe.**
I would like that the configuration schema is validated based on the solver selected. Because based on the solver we select we may want / need some config parameters or other.

**Describe the solution you'd like**
A more flexible json schema structure and validation of the config jsonschema.

**Describe alternatives you've considered**
None

**Additional context**
This structure derived from the jsonschema should be interpreted on cornflow-ui as well.

The issue names no files, tests, or entry points; start by locating the configuration schema and its validation path, then find where cornflow-ui interprets that schema. Done means the schema can express solver-dependent parameters, validation selects the appropriate requirements, and the UI interprets the resulting structure.

Written by the indexing model from the issue text.