Fix duplicate export of OperationalLimitSet

[rcourtier]

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?

No.

What kind of change does this PR introduce?

Bug fix.

What is the current behavior?

• During CGMES import process, OperationalLimitSet attached to an ACLineSegment are duplicated and attached to both sides of the corresponding IIDM Line with the same rdf:ID (saved in a property of the OperationalLimitGroup).
• During CGMES export, OperationalLimitGroup attached to a IIDM DanglingLine are exported twice with the same rdf:ID and attached to both Terminal of the corresponding ACLineSegment.

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

• During CGMES import process, OperationalLimitSet attached to an ACLineSegment are duplicated and attached to both sides of the corresponding IIDM Line. The CGMES rdf:ID and name are stored only on side 1.
• During CGMES export, OperationalLimitGroup attached to a IIDM DanglingLine are exported only once on the Terminal on the network side (so it's not exported anymore on the boundary side).

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

• Yes
• No

Other information:

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
88.9% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud