Allow to use checkLimits methods with LimitReductions

[EtienneLt]

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)

Does this PR already have an issue describing the problem?
No

What kind of change does this PR introduce?
Feature

What is the new behavior (if this is a feature change)?

Add several methods in LimitViolationUtils and Security taking a LimitsComputer as parameter. This allows to use them with the LimitReduction API:

• LimitViolationUtils.checkTemporaryLimits(…);
• LimitViolationUtils.checkPermanentLimit(…);
• Security.checkLimits(…);
• Security.checkLimitsDc(…).

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:
To detect limit violations using some LimitReductions, you need to call one of these methods with an instace of DefaultLimitReductionsApplier, which is a LimitsComputer handling the LimitReductions.

For instance, if you want to call Security.checkLimits(…) with the 2 LimitReductions, limitReduction1 and limitReduction2, you can use the following code:

DefaultLimitReductionsApplier computer = new DefaultLimitReductionsApplier(List.of(reduction1, reduction2));
List<LimitViolation> violations = Security.checkLimits(network, computer);

By default, the reductions which will be applied are the ones defined for the pre-contingency state.
If you want to compute the violations for the state after a specific contingency, you will have to indicate it

For instance, if after the pre-contingency state, you want to compute the post-contingency state for contingency1, you can use the following code:

computer.setWorkingContingency("contingency1");
violations = Security.checkLimits(network, computer);

Note that you don't have to recreate a new DefaultLimitReductionsApplier. I fact, it is more performant to reuse the same object. This LimitsComputer's implementation manages an internal cache and it won't recompute reduced limits if it detects that the reductions applicable for a network element are the same as for the previously studied contingency.

[sonarcloud]

Quality Gate passed

Issues
4 New issues
0 Accepted issues

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

See analysis details on SonarCloud