fix: use propagation view surfaceId for focused input events inside Modal

[JoaoPauloCMarra]

📜 Description

Resolve Android focused-input event surface IDs from the React event propagation view instead of the watched modal window root.

💡 Motivation and Context

ModalAttachedWatcher observes the modal window root while dispatching focused-input events through a separate React view. Resolving the surface ID from the window root returns -1 under Fabric, producing a surface/target mismatch for layout, text, and selection events.

The non-modal path is unchanged because both constructor arguments reference the same React view.

Fixes #1569.

📢 Changelog

Android

• Fixed focused-input event routing inside React Native modals under Fabric

🤔 How Has This Been Tested?

• Android debug assembly with React Native 0.76.2
• Android lint, detekt, and ktlint
• TypeScript, ESLint, and Prettier checks

📝 Checklist

• CI successfully passed
• Library API is unchanged; Android regression coverage was added

[kirillzyusko]

Thank you for PR! Once you address comments we can merge it 🙌

[github-actions]

📊 Package size report

Current size	Target Size	Difference
334276 bytes	334280 bytes	-4 bytes 📉

[github-actions]

1. Incorrect Surface ID Calculation
   Why: The surfaceId is now calculated using eventPropagationView instead of view, which may cause events to be dispatched incorrectly if these views represent different surfaces.
   Fix: Verify that eventPropagationView is the correct source for surfaceId in this context.

2. Potential NullPointerException
   Why: If eventPropagationView is null or doesn't have a valid surface ID, calling UIManagerHelper.getSurfaceId(eventPropagationView) could result in an exception.
   Fix: Ensure that eventPropagationView is always non-null and has a valid surface ID before using it.