CGMES import: make substations property bags distinct when their region is defined twice (in BD and IGM)

[miovd]

Please check if the PR fulfills these requirements (please use '[x]' to check the checkboxes, or submit the PR and then click the checkboxes)

• 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 ? If so, link to this issue using '#XXX' and skip the rest
No

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Bug fix

What is the current behavior? (You can also link to an open issue here)
When the region of a substation is defined twice differently (different IDs in BD and IGM), two substations with the same ID are detected by the importer0

What is the new behavior (if this is a feature change)?
We keep only one substation with the same ID.

Does this PR introduce a breaking change or deprecate an API? If yes, check the following:
No

Other information:

(if any of the questions/checkboxes don't apply, please delete them entirely)

[zamarrenolm]

I prefer to keep the complexity of dealing with multiple references to regions and subregions in the SPARQL query.

Here is an updated version of the query for substations that works with the unit test:

# query: substations
SELECT *
WHERE {
    ?Substation
        a cim:Substation ;
        cim:IdentifiedObject.name ?name .
    # Optional is required to keep the ?Substation variable already bounded in the sub-queries ...
    OPTIONAL {
        {
            SELECT ?SubRegion
            WHERE {
                ?Substation cim:Substation.Region ?SubRegion .
                ?SubRegion a cim:SubGeographicalRegion .
            }
            LIMIT 1
        }
        ?SubRegion cim:IdentifiedObject.name ?subRegionName .
        OPTIONAL {
            {
                SELECT ?Region
                WHERE {
                    ?SubRegion cim:SubGeographicalRegion.Region ?Region .
                    ?Region a cim:GeographicalRegion .
                }
                LIMIT 1
            }
            ?Region cim:IdentifiedObject.name ?regionName .
        }
    }
    # ... But we do not want results where the regions are missing
    FILTER (bound(?SubRegion) && bound(?Region))
}

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

100.0% Coverage
0.0% Duplication