fix: wrong onEnd event on Samsung devices when keyboard gets shown after interactive dismissal

[kirillzyusko]

📜 Description

Fixed wrong event for "end" keyboard movement after interactive dismissal (when keyboard gets shown after interaction).

💡 Motivation and Context

Originally reported by @pioner92 months ago and later raised as an issue by @iankberry

It's a known issue that in onEnd we may get out-of-dated keyboard frame metrics. The fix that I used earlier was postponing the event a little bit if it was interactive dismissal. It fixed the issue for my pixel device in #814

However if we test Samsung device we can clearly see that the bug is reproducible again. In this PR I'm continue to use the idea introduced in #814 and just use larger delay. It fixes the problem, but I'll conduct an exploration for a better/more synchronous code. I started this investigation in #1017 and I plan to return to this PR soon 👀 (but for now we'll merge a workaround)

Closes #1238

📢 Changelog

JS

• added onEnd handler in "Interactive Keyboard" example

Android

• added UIThread constants;
• use .postDelayed() instead of .post() with one frame delay;

🤔 How Has This Been Tested?

Tested manually on Samsung S25+, Android 15 (Remote test lab) in example app.

📸 Screenshots (if appropriate):

Before	After
Screen.Recording.2025-12-12.at.11.31.24.mov	Screen.Recording.2025-12-12.at.11.26.58.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
230358 bytes	230197 bytes	161 bytes 📈