Consider sides when applying limitReductions with IdentifiableCriterion

[olperr1]

Please check if the PR fulfills these requirements

• [X] The commit message follows our guidelines
• [X] 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?

Bug fix

What is the current behavior?

When a LimitReduction is defined using an IdentifiableCriterion (to define a reduction on a voltage level for instance), the reduction is applied on each side of the network element if one of its sides verify the criterion.

What is the new behavior (if this is a feature change)? For IdentifiableCriterion, the reduction is applied only on the side(s) verifying the criterion.

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

• [ ] Yes
• [X] 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:

[sonarcloud[bot]]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

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

See analysis details on SonarCloud