Add logic to check for incompatible parameters

[rvhonorato]

You are about to submit a new Pull Request. Before continuing make sure you read the contributing guidelines and that you comply with the following criteria:

• You have sticked to Python. Please talk to us before adding other programming languages to HADDOCK3
• Your PR is about CNS
• Your code is well documented: proper docstrings and explanatory comments for those tricky parts
• You structured the code into small functions as much as possible. You can use classes if there is a (state) purpose
• Your code follows our coding style
• You wrote tests for the new code
• tox tests pass. Run tox command inside the repository folder
• -test.cfg examples execute without errors. Inside examples/ run python run_tests.py -b
• PR does not add any dependencies, unless permission granted by the HADDOCK team
• PR does not break licensing
• Your PR is about writing documentation for already existing code 🔥
• Your PR is about writing tests for already existing code

---

This PR adds a logic to check for parameter incompatibilities.

For example; with #918 I added a new parameter called less_io however you cannot use this parameter together with mode=batch.

So now you can define a new incompatible property of a given parameter in the haddock.modules.defaults.yaml;

less_io:
  # ...
  incompatible:
    mode: batch

Which will then be validated when the run is being setup.

[sverhoeven]

In clustrmsd module the value of criterion parameter determines which other module parameters are ignored see

haddock3/src/haddock/modules/analysis/clustrmsd/defaults.yaml

Line 50 in a11a7c3

long: Value of cutoff cophenetic distance. When criterion is maxclust, this value is ignored.

. Could we use incompatible parameters there as well? Or use clustrrmsd approach here?

[VGPReys]

In clustrmsd module the value of criterion parameter determines which other module parameters are ignored see

haddock3/src/haddock/modules/analysis/clustrmsd/defaults.yaml

Line 50 in a11a7c3

long: Value of cutoff cophenetic distance. When criterion is maxclust, this value is ignored.

. Could we use incompatible parameters there as well? Or use clustrrmsd approach here?

I don't know, because they have default values, and only in some case (based on criterion value) some parameters will be used but not the other ones.

[amjjbonvin]

We will have to remember to edit the default.yaml files when needed to define incompatible parameters, but now at least the machinery to check those is in place - nice!

cannot add code and review at the same time