fix(react-components): optimize styled node collection diff check on re-render

[haakonflatval-cognite]

Type of change

Jira ticket 📘

https://cognitedata.atlassian.net/browse/

Description 📝

Optimize style-difference check. This severely hampered performance on model

{
    modelId: 3282558010084460,
    revisionId: 4932190516335812
}

in 3d-test. This is likely due to the large number of mapped equipment.

Essentially, this optimization ensures index sets are not reconstructed unnecessarily, but stored properly from when edges are constructed.

Update: It seems like I (using Firefox on Linux) am the only one having these severe performance problems. I'm adding a video to document what the experience is at my end:

slow_click.mp4

How has this been tested? 🔍

In FDX locally.

Test instructions ℹ️

Open https://apps.cognite.com/explore/FDX_Boys/fdx-boys/2/Equipment/fdx-boys/Gokhan-2878543855731702-IAA?aiSearch=false&viewMode=3d and notice how clicks on Ivar Aasen (the oil platform) are sort-of slow.

Use this PR in FDX locally, and see how clicks are notably faster.

Checklist ☑️

• I am proud of this feature.
• I have performed a self-review of my own code.
• I have added PR type (Feat, Bug, Chore, Test, Docs, Style, Refactor) to the PR title.
• I have manually tested this for different scenarios (different models, formats, devices, browsers).
• I have commented my code in hard-to-understand areas.
• I have made corresponding changes to the public documentation.
• I have added unit and visuals tests to prove that my feature works to the best of my ability.
• I have refactored the code for readability to the best of my ability.
• I have checked that my changes do not introduce regressions in the public documentation.
• I have outlined any known defects / lacking capabilities in the contents of this PR.
• I have listed any remaining work that should follow this PR in the description or jira/miro/etc.
• I have added TSDoc to any public facing changes.
• I have added "developer documentation" in any package README.md that is related / applicable to this PR.
• I have noted down and am currently tracking any technical debt introduced in this PR.
• I have thoroughly thought about the architecture of this implementation.
• I have asked peers to test this feature.