fix: findNodeHandle on the web platform

[IvanIhnatsiuk]

📜 Description

In the new version of react-native-web they added an error throw if you try to use findNodeHandle from react-native https://github.com/necolas/react-native-web/blob/922c134f2b7c428cc19daaeb3cac4b6a4c8ec6a3/packages/react-native-web/src/exports/findNodeHandle/index.js#L11. So I created a findNodeHandle utility that uses react-native's findNodeHandle for the native platform and returns Node or null for web.

💡 Motivation and Context

This library should work well on all platforms

📢 Changelog

JS

• added findNodeHandle util

🤔 How Has This Been Tested?

tested in a web browser

📸 Screenshots (if appropriate):

Before:

Screen.Recording.2025-04-10.at.11.20.20.mov

After:

Screen.Recording.2025-04-10.at.11.19.08.mov

📝 Checklist

• CI successfully passed
• I added new mocks and corresponding unit-tests if library API was changed

[github-actions]

📊 Package size report

Current size	Target Size	Difference
177281 bytes	176200 bytes	1081 bytes 📈

[kirillzyusko]

Since I don't support web - it's okay to return element as node-handle.

On web for registerEventHandler I use mock, KeyboardAwareScrollView also will work with these changes (it will compare node-handle with null, so will be false and will not work on web (and it's expected)).