This reverts commit 594cd772cd.

* pass props for topBar background component

* refactored custom components

* pass props for topBar background component

* refactored custom components

* refactored RNNOptions object

* Use margin to control component position relative to TopBar

RelativeLayout rules caused excessive CPU usage due to issues with RN's
keyboard detection mechanism (based on global layout listener)

* Skip custom transition e2e on Android

* Improved the clarity of the top-level API doc (#2984)

I clarified some of the language here so that it is easier for the beginner to understand. (It was a little bit awkward before)

* Increase gradle daemon process memory

* Disable Orientation test on Android

* Fix SideMenu e2e

* Fix popTo

* Use margin instead of RelativeLayout rules to align component to BottomTabs

Rules caused excessive CPU usage due to RN issue with global layout listener
and keyboard visibility detection.

* Update README.md

for triggering build

* Update README.md

* Consolidate pop and animatePop

* Update top-level-api.md ... more copyediting. (#3002)

Further clarification of some of the top level API stuff.

* popTo animates top screen

* Refactor component options on Android

* Stop processing passProps from options

* removed comments

This is working on the screen API too, however it's not included in screen API, only on top-level screen

Add downloads per week

Further clarification of some of the top level API stuff.

for triggering build

Rules caused excessive CPU usage due to RN issue with global layout listener
and keyboard visibility detection.

I clarified some of the language here so that it is easier for the beginner to understand. (It was a little bit awkward before)

RelativeLayout rules caused excessive CPU usage due to issues with RN's
keyboard detection mechanism (based on global layout listener)

PR #2658 removed layout params from the child views, which causes
component children to receive zero width. Stack children work since
they don’t need the layout params.

There's a roundabout manner of obtaining the react context on initialisation that is null on some instances (https://github.com/wix/react-native-navigation/issues/2695), including errors on startup that prevents debugging on console. (For instance, throwing an error on index before starting the app)

It is solved by sending the same context given on method onReactContextInitialized, instead of discarding it and calling getReactContext.

* for iOS

* first try for android

* iOS indent

* Android Indent

* Update platformSpecific.android.js

* Update NavigationReactModule.java

* Update NavigationCommandsHandler.java

* Update platformSpecificDeprecated.android.js

* Update platformSpecificDeprecated.ios.js

closes #2966

listener was invoked twice

Screen presentation logic in stack should be moved to a dedicated presenter