TCK: Remove reference comparisons for Ratio/PhaseTapChangers

[AbdelHedhili]

Please check if the PR fulfills these requirements

• [x] The commit message follows our guidelines
• [x] Tests for the changes have been added (for bug fixes / features)
• [ ] Docs have been added / updated (for bug fixes / features)

What kind of change does this PR introduce? changes TCK test

What is the current behavior? There are tests that compare Ratio/PhaseTapChanger by reference and expect that we keep the same reference for these objects

What is the new behavior (if this is a feature change)? Remove these checks that are implementation dependent

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

• [ ] Yes
• [X] No

[sonarcloud[bot]]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud