Avoid useless peruniting/de-peruniting

[geofjamg]

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)
Unnecessary power per uniting is responsible for loss of precision and uncontrolled network notifications when saving/restorating state.

What is the new behavior (if this is a feature change)?
We do not anymore perunit/de-perunit when setting of getting active/reactive power in the LF data model.

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)

[annetill]

I have made some changes, that you have to check of course. We have an exception in the Lf world with getAbsVariableLoadTargetP() in aggregated loads because we don't need it. But it could be confusing...

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

100.0% Coverage
0.0% Duplication