feat(react-components): clicked node hook

[haakonflatval-cognite]

Type of change

Jira ticket 📘

https://cognitedata.atlassian.net/browse/UX-1147

Description 📝

Adds a useClickedNode hook which uses react-query under the hood to listen to and fetch data related to Cad Node clicking.

Known issues:

• On clicking the second node after one is already clicked, the hook will spurt out three updates:
  • The first result once again
  • undefined
  • The result belonging to the second node

This may just be alright, but feels unnecessary

How has this been tested? 🔍

In the story.

Test instructions ℹ️

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.

[Savokr]

Looks really good but a few things to consider.

[Savokr]

Looks good!

[Savokr]

LGTM