Discrepant `cim:` namespaces between CGMES and NCP

[VladimirAlexiev]

@Sveino @EduardoRelAlg @griddigit-ci

CGMES uses the old (CIM17) namespace:
https://github.com/entsoe/application-profiles-library/tree/main/CGMES/CurrentRelease/RDFS

xmlns:cim="http://iec.ch/TC57/CIM100#"
xml:base ="http://iec.ch/TC57/CIM100"

NCP uses the new (version-free) namespace:
https://github.com/entsoe/application-profiles-library/tree/main/NCP/CurrentRelease/RDFS

 xmlns:cim="https://cim.ucaiug.io/ns#"
 xml:base="https://cim.ucaiug.io/ns" 

This causes term duplication between profiles.
(The following few examples come from some analysis of Statnett production data. Of course, NCP refers to a LOT more cim; terms.)

For example, er:Package_EquipmentReliabilityProfile defines and uses:

@prefix cim-new: <https://cim.ucaiug.io/ns#> .
cim-new:Currency                       a rdfs:Class ;
cim-new:CurveStyle                     a rdfs:Class ;
cim-new:OperationalLimitDirectionKind  a rdfs:Class ;
cim-new:UnitMultiplier                 a rdfs:Class ;
cim-new:UnitSymbol                     a rdfs:Class ;

Whereas EQ defines and uses:

@prefix cim: <http://iec.ch/TC57/CIM100#> .
cim:Currency                       a rdfs:Class ;
cim:CurveStyle                     a rdfs:Class ;
cim:OperationalLimitDirectionKind  a rdfs:Class ;
cim:UnitMultiplier                 a rdfs:Class ;
cim:UnitSymbol                     a rdfs:Class ;

This means that CGMES and NCP in this release cannot be used together (!!!!!)