fix: support NestedScrollView in KeyboardAwareScrollView

[kirillzyusko]

📜 Description

Added support for NestedScrollView for KeyboardAwareScrollView.

💡 Motivation and Context

When users enable useNestedScrollViewAndroid feature flag, then ReactNestedScrollView is used:

      if (ReactNativeFeatureFlags.useNestedScrollViewAndroid()) ReactNestedScrollViewManager()
      else ReactScrollViewManager(),

As a result our condition returns false (casting of parentView to ReactScrollView is failing):

if (parentView is ReactScrollView && parentView.scrollEnabled) {

So we never recognize the ReactNestedScrollView as a ScrollView and because of that condition is evaluated as true:

        // input belongs to ScrollView
        if (layout.value?.parentScrollViewTarget !== scrollViewTarget.value) {
          return 0;
        }

So scrolling never works.

In this PR I created small extension called View.isEnabledReactScrollView() that checks both cases: ReactScrollView and ReactNestedScrollView.

This implementation had technical difficulties, because ReactNestedScrollView is not available in earlier RN versions (was introduced only in RN 0.85+) so I had to use reflection, because we can not use direct class references as it may be not available in all framework versions.

Closes #1537

📢 Changelog

Android

• added View.isEnabledReactScrollView() extension that checks both ReactScrollView/ReactNestedScrollView cases;
• use isEnabledReactScrollView() condition instead of previous check;

🤔 How Has This Been Tested?

Tested via CI (e2e tests).

📸 Screenshots (if appropriate):

📝 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
338857 bytes	338428 bytes	429 bytes 📈

[github-actions]

1. Potential Reflection Failure in ScrollView Detection
   Why: The isEnabledReactScrollView function uses reflection to access private fields and methods, which can fail if the class structure changes, leading to incorrect ScrollView detection.
   Fix: Replace reflection with public APIs or ensure compatibility across React versions.

2. Incorrect ScrollEnabled State Detection
   Why: If both scrollEnabledGetter and scrollEnabledField fail, isScrollEnabled returns false, potentially missing actual scrollable states.
   Fix: Add fallback mechanisms or use observable properties to accurately detect scroll enabled state.