CNEC geographical filter for CSA Profiles import

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

1. The FlowCNECs naming convention has slightly evolved to included the TATL duration for curative CNECS in order to avoid conflicts of two CNECs having the same id if two TATLs correpond to the same instant (new pattern: TSO_AE (mRID) - TSO_CO - instant - TATL duration)
2. A geographical filter for CNECs was added for the import of CSA profiles. During CSA profiles import, if the geographical filter is activated, all the curative CNECs the network elements of which are defined in countries different from the countries where the associated contingency is defined will be ignored. This is added to the CRAC creation context for transparency. This allows the users to filter out some CNECs that could be too numerous otherwise.
3. A CsaCracCreationParameters extension was added. The only current parameter is used to activate/deactivate the geographical filter. By default, the filter is disabled. If no CSA extension is provided with the CracCreationParameters, the filter is also considered to be disabled. Below is an example of JSON-serialized CsaCracCreationParameters:

{
  "crac-factory" : "CracImplFactory",
  "extensions" : {
    "CsaCracCreatorParameters" : {
      "use-cnec-geographical-filter": true
    }
  }
}

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

• Yes
• No