fix: Disable interactions on minimal required subroot

[kmichalikk]

Description

Fixes #3307

This PR changes the logic for setting userInteractionsEnabled = false for the time of screen transitions. Currently, when transition happens, the whole UIWindow gets disabled. This included the time when the whole stack is detached from the window, for instance, when changing the tab in BottomTabs. This unnecessarily removes the ability to click through tabs for the time of the transition. Moreover, in some cases on hot reload, the call to disable the interactions is not matched with re-enabling them. This PR fixes both issues by introducing a helper class with one instance shared across screens, that finds an appropriate view to disable, and stores a reference to it, to make sure the correct one is re-enabled.

The final attempt disables interaction for RNSScreenStack's first subview, which wraps navigation header and screen content, and adds a temporary gesture recognizer for RNSScreenStackView which captures swipe gestures and does nothing so the gestures are not propagated further (for instance, to outer stack when one is nested in another, which would result in the whole stack being dismissed if user happens to swipe again mid transition).

Changes

Set userInteractionsEnabled = false on RNSScreenStack subview. Temporarily add UIPanGestureRecognizer to sink all gesture event.

Test code and steps to reproduce

Use BottomTabsTest to verify that BottomTabs can be clicked through, and Test3093 to verify that the logic for stack doesn't change.

[focux]

Is there any ETA for this to be merged 👀

[kkafar]

This looks sensible. I did some manual testing & it seems that "regular" scenarios are working fine.

@KrzysztofWojnar could I add this to your backlog? Would be nice to test this on more "complex" navigation scenarios (modals & push interlaced, tabs, split, etc.)