Rework of LineConnectionAction to TerminalsConnectionAction

[annetill]

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, but line connection action support in powsybl-open-loadflow is much more complex that expected. Indeed, the real issue is that sometimes as remedial action, we want:

• Open or close a line ;
• Open or close a line at one side only.

My understanding of the design is that we have to give open status both both side, always. Even if the terminal status (open or close) is not changed through the action.

What kind of change does this PR introduce?

Feature.

What is the current behavior?

See above limitations of LineConnectionAction

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

Removal of LineConnectionAction, reworked in new more generic TerminalsConnectionAction.

The side can be optionally specified. Not providing the side means operating all terminals. Furthermore, the element can be anything: line, transformers, tie line (through dangling lines), hvdc (through converter stations), etc. And more like generators, loads, etc....

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:

maybe the identifiable type must be provided to ease integration, this would eventually be subject of another PR

[sonarqubecloud]

Quality Gate passed

Kudos, no new issues were introduced!

0 New issues
0 Security Hotspots
90.6% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud