feature(RAO Result): convert to operator strategy

[bqth29]

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)
• A PR or issue has been opened in all impacted repositories (if any)

Does this PR already have an issue describing the problem?

What kind of change does this PR introduce?
Allow to convert a RAO Result to a list of Operator Strategies and Actions to easily run a security analysis based on the outputs of the RAO.

Simply run RaoResult::getOperatorStrategies

What is the current behavior?

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

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:

[pet-mit]

maybe let's accept once and for all that a RaoResult depends on a Crac (thus we can add a RaoResult.getCrac() method) and that a Crac depends on a Network (Crac.getNetwork())
@phiedw @Godelaine thoughts ?

[sonarqubecloud]

❌ The last analysis has failed.

See analysis details on SonarQube Cloud

[bqth29]

There is currently no way to serialize a Switch Pair Action because it is not part of PowSyBl core ecosystem. I see two ways of doing it:

1. implement switch pairs in core
2. remove switch pairs API in OpenRAO and replace it by two switch actions

@pet-mit do you have an opinion on this matter?

I guess a key point is to know whether a switch pai is to be considered as one elementary action or two

[sonarqubecloud]

Quality Gate failed

Failed conditions
43.1% Coverage on New Code (required ≥ 80%)

See analysis details on SonarQube Cloud

[pet-mit]

There is currently no way to serialize a Switch Pair Action because it is not part of PowSyBl core ecosystem. I see two ways of doing it:

1. implement switch pairs in core
2. remove switch pairs API in OpenRAO and replace it by two switch actions

@pet-mit do you have an opinion on this matter?

I guess a key point is to know whether a switch pai is to be considered as one elementary action or two

why do you need to serialize a switch pair action as one powsybl action ?
it should be enough to consider it as two elementary (powsybl) actions like it is done under the hood in the CracImpl