CGMES import: import TATL shortName or name, not ID + CGMES export: fix on LoadingLimitType and LoadingLimit names

[miovd]

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

What kind of change does this PR introduce?

Bug fix/enhancement on limits naming during CGMES import/export

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

No

Other information:

[annetill]

You must find a way to keep original ids (with alias) in order to export a CGMES file that comes from a CGMES file. It seems that there are lost.

[miovd]

You must find a way to keep original ids (with alias) in order to export a CGMES file that comes from a CGMES file. It seems that there are lost.

There were already lost but it does not seem to me that they are supposed to be persistent (same thing for OperationalLimitSet). It was not really useful for me in this case to keep the IDs.

[zamarrenolm]

You must find a way to keep original ids (with alias) in order to export a CGMES file that comes from a CGMES file. It seems that there are lost.

There were already lost but it does not seem to me that they are supposed to be persistent (same thing for OperationalLimitSet). It was not really useful for me in this case to keep the IDs.

Agree on moving the persistence of identifiers related to operational limits out of this PR. If required, it should be done in a separate one.

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

100.0% Coverage
0.0% Duplication