* Rename to onChildWillAppear

* update roadmap

on clicking the outside of the sideMenu area sideMenu not closing,
because there is a problem in the code which i modified now

Each animation (push, pop etc) can be enabled or disabled separately

I made the text a little more punchy and easy to read.

The following  https://github.com/wix/react-native-navigation/pull/3006 implemented this functionality

This reverts commit db567ea7b3.

This reverts commit ee48da2e7c.

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

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)