[CSA] Multiple TATLs and 3 curatives instants

[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)

What kind of change does this PR introduce?

• Automatic creation of three curative instants when importing CRAC from CSA Profiles (respectively named curative 1, curative 2 and curative 3)
• Curative remedial actions are created for all three curative instants
• New FlowCNEC instant definition based on all the TATLs (see docs for more details)
• Extension of CSA CRAC creation parameters to account the new TATL-instant association algorithm (application time of each curative batch, choice for each TSO whether to use the PATL in the final state)

{
  "crac-factory" : "CracImplFactory",
  "extensions" : {
    "CsaCracCreatorParameters" : {
      "capacity-calculation-region-eic-code": "10Y1001C--00095L",
      "sps-max-time-to-implement-threshold-in-seconds": 0,
      "use-patl-in-final-state": {
        "REE": false,
        "REN": true,
        "RTE": true
      },
      "cra-application-window": {
        "curative 1": 300,
        "curative 2": 600,
        "curative 3": 1200
      }
    }
  }
}

What is the current behavior?

• Only one curative instant
• Instant of FlowCNEC is simply determined by limit type (PATL / TATL) and duration:
  • 0 = curative
  • ]0, 60] = outage
  • ]60, 900] = auto
  • 900+ = curative

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

• Three curative instants (curative remedial actions are systematically created for all three)
• Instant of FlowCNEC is determined by all available limits (see docs) thanks to a helper class FlowCnecInstantHelper
• One FlowCNEC is created for each side (a single FlowCNEC created from CSA profiles can no longer have thresholds on both sides)

This behavior is to account for interconnection lines that may have different limits on both sides and thus thresholds of different instants

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

• Yes
• No

Other information:
Small refactoring of the FlowCnecCreator class.

[MartinBelthle]

miam les conflits

[phiedw]

misclicked last review