[WIP] Add a check on minQ <= maxQ

[So-Fras]

Please check if the PR fulfills these requirements

• The commit message follows our guidelines
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

What kind of change does this PR introduce?
Quality

Does this PR introduce a new Powsybl Action implying to be implemented in simulators or pypowsybl?

• Yes, the corresponding issue is here
• No

What is the current behavior?
There is no check to ensure minQ <= maxQ in a ReactiveCapabilityCurve Point.

What is the new behavior (if this is a feature change)?
A check is added to ensure minQ <= maxQ in a ReactiveCapabilityCurve Point.
An excpetion is thrown when minQ > maxQ.

Does this PR introduce a breaking change or deprecate an API?

• Yes
• No

If yes, please check if the following requirements are fulfilled

• The Breaking Change or Deprecated label has been added
• The migration steps are described in the following section

What changes might users need to make in their application due to this PR? (migration steps)

Other information:

• Is it really a change in IIDM since no new attribute is added? Maybe it is since an IIDM file with a minQ > maxQ will not be processed the same way as before...
• Should we throw an exception or should we "fix" one of the values (take the smallest value both for minQ and maxQ to be conservative?) with a warning to make the model more robust?

[sonarqubecloud]

Quality Gate passed

Issues
1 New issue
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[geofjamg]

Yes this is a breaking change as you won't be able to load old files without any exception. You can add this kind of change BUT only in a new version of IIDM and keeping old behaviour (do nothing) for other IIDM versions.

[flo-dup]

There's a related TODO written in 2017 (to plan it for IIDM v1.1!!) in the corresponding adder, and a @Disabled in a unit test in AbstractReactiveCapabilityCurveTest. Could you remove them?

This should be only activated for next IIDM version. There should be a check in the importer based on the IIDM version to flip or not.