Update usage of findDOMNode

[martijnrusschen]

Description:
This pull request addresses an issue where the use of ReactDOM.findDOMNode was causing compatibility problems in certain scenarios. To resolve this, we have updated the code to use findDOMNode directly.

Changes Made:

• Replaced instances of ReactDOM.findDOMNode with findDOMNode throughout the codebase.
• This change ensures improved compatibility with the latest React versions and eliminates potential issues related to the deprecated ReactDOM.findDOMNode method.

[pullrequest]

⚠️ This pull request was not sent to the PullRequest network because the title contains "draft:".

[codecov]

Codecov Report

Merging #4190 (21f1d81) into main (8b28bb7) will not change coverage.
The diff coverage is n/a.

❗ Current head 21f1d81 differs from pull request most recent head fc64949. Consider uploading reports for the commit fc64949 to get more accurate results

@@           Coverage Diff           @@
##             main    #4190   +/-   ##
=======================================
  Coverage   96.54%   96.54%           
=======================================
  Files          27       27           
  Lines        2374     2374           
  Branches      966      966           
=======================================
  Hits         2292     2292           
  Misses         82       82           

[pullrequest]

✅ This pull request was sent to the PullRequest network.

---

Check the status or cancel PullRequest code review here.

[pullrequest]

PullRequest Breakdown

Reviewable lines of change

+ 114
- 113

100% JavaScript (tests)

Type of change

Feature - These changes are adding a new feature or improvement to existing code.

	1 Message
✅	It looks like the description for this pull request is either blank or very short. Adding a high-level summary will help our reviewers provide better feedback. Feel free to include questions for PullRequest reviewers and make specific feedback requests.

[Zarthus]

Changes seem harmless and LGTM, the CI seems happy too :)