Refactor PowerFactory object reference

[geofjamg]

Signed-off-by: Geoffroy Jamgotchian geoffroy.jamgotchian@gmail.com

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, ...)
Design fix

What is the current behavior? (You can also link to an open issue here)
When reading from DGS file, object reference are modeled by an INTEGER64 attribute, which is wrong. There are INTEGER64 attributes that are not object references and there is a dedicated type (see PF C++ API) for that.

What is the new behavior (if this is a feature change)?
A new DataObjectRefhas been added to handled non resolved object references and a global data object index has also been added to allow reference resolving (and also avoid recomputing object index in converter).

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

• The Breaking Change or Deprecated label has been added
• The migration guide has been updated in the github wiki (What changes might users need to make in their application due to this PR?)

Other information:

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

[marqueslanauja]

Only two minor things,
The method traverseAndReference of the DataObject class is not used after your refactor and can be deleted.
Maybe, to be clearer, change DataAttributeType.OBJECT to DataAttributeType.OBJECTREF and DataAttributeType.OBJECT_VECTOR to DataAttributeType.OBJECTREF_VECTOR

[geofjamg]

Only two minor things, The method traverseAndReference of the DataObject class is not used after your refactor and can be deleted. Maybe, to be clearer, change DataAttributeType.OBJECT to DataAttributeType.OBJECTREF and DataAttributeType.OBJECT_VECTOR to DataAttributeType.OBJECTREF_VECTOR

I removed traverseAndReference.
For object type naming, I think we should keep same naming as c++ API.

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

93.7% Coverage
0.0% Duplication