[WIP] Fix SA reports in MT

[vidaldid-rte]

NOTE: needs this PR to build: https://github.com/powsybl/powsybl-core/pull/3303

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? Some issues are reported in #1167

What kind of change does this PR introduce? There are some issues with Security Analysis in MT:

• Reports contain duplicated entries for network loading and precontingency run
• PostContingency results are split in different node (one per thread)
• Operator Strategies are not supported (an exception is thrown because a contingency is not in the partition of a given thread)

This PR fixes those issues

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

One report node per CC that contains in order: One instance of network loading One instance of precontingency run All postcontingency results for that CC

The report is the same in single thread or multithread except that the contingency order may change.

In multi-thread mode, the check to verify that an operator strategy is associated to a contingency is not performed.

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

• [ ] Yes
• [X] No

[sonarqubecloud[bot]]

Quality Gate passed

Issues
3 New issues
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

[vidaldid-rte]

Reducing the list of reviewers now that the implementation is based on report postprocessing.

[sonarqubecloud[bot]]

Quality Gate passed

Issues
9 New issues
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