[BREAKING] Call Navigation.events().bindComponent(this) to listen to lifecycle events

This commit introduces breaking changes to the way components listen to RNN events.


Background

Up until now, components could handle navigation events by implemented a set of callbacks:
* componentDidAppear
* componentDidDisappear
* onNavigationButtonPressed
* onSearchBarUpdated
* onSearchBarCancelPressed

While this worked fine for the most part, this was completely broken for HOCs as RNN invoked these methods only on the registered component (top most HOC), leaving it to the user to propagate these events down the HOC chain. See the discussion in #1642 for more details.


Solution

In order to support HOC use case, we're introducing a new api which will let any Component bind itself to receive navigation events:

```js
class LifecycleScreen extends Component {
  constructor(props) {
    super(props);
    this.subscription = Navigation.events().bindComponent(this);
  }

  componentWillUnmount() {
    // The subscription is removed automatically when components unmount, but they can be explicitly removed as well by calling `this.subscription.remove(); `
  }
}
```

It's still the users responsibility to propagate the `componentId` down the HOC chain, but by binding a component to RNN, it will be able to handle events as expected. Multiple components can be bound for the same `componentId`.


Consolidate event names

* onNavigationButtonPressed -> navigationButtonPressed
* onSearchBarUpdated -> searchBarUpdated
* onSearchBarCancelPressed -> searchBarCancelPressed

Related to #3054

[BREAKING] Buttons refactor

* Support setting single button
```js
  topBar: {
    rightButtons: {
    }
  }
```
* [BREAKING] Rename button.title to button.text

* Set TopBar default background color (white)

Command animations did not take default options into account when resolving animation options.
This commit fixes that, TopBar options still need to be addressed.

This reverts commit 6c451d3744.

This reverts commit fc493775eb.

This commit introduces an option to control the way components are pushed into the stack.
When pushing components into a stack, they are pushed the moment they are measured.
If `waitForRender` is true, components will be pushed only after the initial render.

api:

```js
options: {
  animations: {
    push: {
      waitForRender: true
    },
    showModal: {
      waitForRender: true
    }
  }
}
```

`largeTitle: true` is not valid and throws error

Unmount react views when bundle load completes

Users providing their own ReactNativeHost implementations should implement BundleDownloadListenerProvider
and make sure they set DevBundleDownloadListener when ReactInstanceManager.

* Provide findViewController api method

* Fix merge changes

* Optional resizeMode

* Update Element typings

If ReactContext is null, the event is emitted when onReactContextInitialized is invoked. Closes #3392

* Constants support

* Change Navigation.constants() to an async function on Android

Also added topBarHeight and bottomTabsHeight

I was unable to compile because I use multidex and this line of code force the multidex library to be version 25.4.0 when the latest for this one is 1.0.3. This little fix may save a lot headaches.

title was renamed to text

We need handle situation where currently emitAppLaunched is being called with null context.
Related to #3392

* Refactored bottomTab and bottomTabs

* Initial commit before switching to our fork of AHBottomNavigation

* Bump AHBottomNavigation version

* More work on BottomTab options

Need to merge some child options when a child is attached to parent

* Fix tests

* DefaultOptions refactor

* defaultOptions are now merged before applying options
* Handle BottomTab options in dedicated presenter
* Create BottomTabs in BottomTabsController.createView() instead of constructor

* Set bottomTab TypeFace

* Update Android installation guide

* fixed unit tests

* Fix unit tests

Kind of a workaround

* Handle NPE in getPreferredHeight

If a view hasn't been attached yet, return 0 height

* Apply BottomTab text and icon color individually

wix-playground/AHBottomNavigation does not support setting color for the entire tab (icon and text),
instead it supports setting color individually to text and icon. Another change is that it no longer supports
default color for icons. If icon color is undefined - it won't tint the icon.

* Add getCurrentChild to ParentController contract

* Clear backButton when setting stack root

* Add  ViewController.resolveCurrentOptions

resolveCurrentOptions merges the controllers options with all of its current children

* StackController refactor

* Create pushed child view only in StackController.createView
* When initialising a stack with multiple children, only create the top child's view
* StackController constructor now accepts children
* When pushing child to stack, apply options that change LayoutParams

* Apply BottomTabs layout options when tab views are created

* bototmTab changes in iOS

* options fix

* Fixes options propagating