This commit includes two fixes to YellowBox handling:

1. RN started throwing exceptions when views added in JSX were removed from hierarchy.
    We could probably use UiManager to fiddle around with the yellow box, either removing it or making
    it hidden and allow touch events to pass through it. For now, we continue removing yellow boxes from hierarchy
    and we replace the removed yellow boxed with dummy views.
2. A “Dismiss All” button was recently added, we remove that as well.

Fixes #4035

Destroy navigation activity layouts on catalyst instance destroy

addresses #2331 & Microsoft/react-native-code-push#1144

* Use resolved options when applying options in ChildController
* mergeOptions only if view is visible

passProps are handled in Js and should not go over the bridge as they aren’t serialisable.
Fixes #3969

Options are handled in Js and should not be passed over the bridge as that may
cause serialisation errors. Omitting passProps reduces the amount of data passed over the
bridge as well.

The motivation behind this feature was to warn when a user declared a button but forgot register
a handler in a component to handle button press event.
Since buttons can be handled globally using Navigation.events().registerNavigationButtonPressedListener, this feature
is meaningless.
closes #4017

Lists are a crucial component to almost every single app out there. This example contains a flatlist inside a bottomTab layout with a sidemenu too (basically as complicated as a screen would get).

Avoid listing .json files

This is mentionned in https://github.com/wix/react-native-navigation/issues/3905

add missing topBar

When a stack’s child appears we previously applied the child’s options on the stack, without merging the child and the stack’s options.
This commit fixes this by resolving options of all visible children when applying child options.

This commit fixes #4045, which revealed a design flaw in the options applying logic.
Child options are applied when a ViewController.onViewAppeared is invoked.
A ViewController's appearance is determined from a GlobalLayoutListener.

Consider the following layout hierarchy:
BottomTabs > Stack > Component

onViewAppeared will be triggered for the BottomTabs first, then for the Stack and last for the component.
This means that if the Stack and the Component options will be applied consecutively which in some cases
might case flickering, mostly when drawBehind options are applied.

The button which was added for `setRoot should not remove overlay` wasn’t fully visible on Android
and Detox detected it as not visible.

* Detached options from presenters, design improvments for LayoutProtocol

* fixes topBar.background.clipToBounds

* Fixes e2e

* Fixes unit tests

* Homogeneous constructors for parent and child view controllers

* Handle parent options merging with children in optionsResolver

* Fix topBar.background.clipToBounds

* Removed unnecessary options merging

* Fixes shared element transition

* Fixed sideMenu inside bottomTabs

Copied a bad answer from stack overflow 🤦‍♂️

* Fix Jenkins link badge

* Revert "Fix Jenkins link badge"

This reverts commit 78e8ef56f1.

* Removed topBar.transparent and added transparent color support for topBar.background.color

* fix unit tests

This test checks if mergeOptions are applied correctly on SideMenu child contained inside BottomTabs layout

* Check if value is double instead of expecting exception

* Added try catch block to compensate for React51 exception on getDouble

Use Case: When exposing the layout, other android code can check what kind of layout it is and react accordingly, fx:
```
if (activity.getLayout() instanceof BottomTabsLayout) {
    // ...
}
```

Now that BottomTabs options are applied on self, they need to be cleared after applying initial options.

Relying on WRAP_CONTENT caused rare bugs where the TopBar would appear stretched due to flex issues
when a react component was displayed in the title.
Another reason for this change is that we don’t need to wait for the TopBar to measure itself when its height needs to be taken
into account, for example when animating it or when positioning views below it.

* Fix ability to add color for back button

* Change docs because color can be used with iOS too

* Simplify code more

* Move icon logic to one function

* Make returning more clear

* Remove title setting because it is in setBackItem

* Make setBackItem function more clear

* Looks like the if is not needed

* Update RNNBackButtonOptions.m

* Update RNNBackButtonOptions.m

* Renamed RNNRootViewProtocol to RNNParentProtocol and added RNNLeafProtocol

* fixed unit test

* Better options resolving

* Revert "Revert "Refactor options (#3962)""

This reverts commit c266041b85.

* Revert "Revert "Fixes shared element transition""

This reverts commit 005f039f7c.

* Revert "Revert "Adresses #3963 - stack options applied to children""

This reverts commit be09cb0e9a.

* Revert "Revert "Added unit test coverage for RNNNavigationController""

This reverts commit 199cebd221.

* Merge stack options

This commits adds support for merging stack options by the stack’s componentId

Also while I’m at it - use fade animation when setting root

* Merge BottomTabs options

Merge BottomTabs options when calling mergeOptions with BottomTabs componentId

* Fixes options

Only text size was taken into account

Mostly leftover code related to shared element transition