Now iOS e2e is legitimately broken :)

* add back button to screens pushed to stack
* resolve tab icon from root screen, instead of first pushed screen
* omit components object from tabs

* Make detox android test suit pass

Disabled emulator animations due to limitation of espresso/detox which can't wait until
a push/pop animation ends

* Fix orientation parsing and enable detox orientation tests

* remove only

* Fix BottomTabs testId

* Support user orientation

* Fix rightButtons testId

* Add Modals tests

* e2e fix ios

* update api jsdoc

* iniline some properties

* add typedoc

* remove typedoc

* try again with typedoc

* explicit types

* docs

* try handlerbars

* working on docs

* update docs

* html

* removed old md

* trying stuff

* fix lint

* working on docs

* trying with themes

* something works

* trying to use automatically

* working on docs

* docs

* docs

* docw

* auto docs

* rename

* local-docs no cache

* automating

* ts-node

* working on something cool

* temp

* try fix travis

* Revert "try fix travis"

This reverts commit 5bcb54659b.

* removed dead files

* main readme inside docs

* softlink

* softlink

* docs working

* Initial orientation implementation on Android

* Disable custom animations for now

* FIx OverlayManager

Keep view references instead of View id as id's can change by react

* Work on ModalStack

* resolve dismissModal promise after dismiss ends
* Send didDisappear when Modal is displayed
* Send didAppear to root when Modal is dismissed
* Introduce new API:
  * onViewLostFocus
  * onViewRegainedFocus
* Fix MockPromise - it can be used only once
*

* Add support for react-native 0.52.0

* Refactore a bit

1. Rename `DevCommandsHandlerProxy` to `DevHelperProxy` so it reflects the changes in RN. See d19afc73f5 .
2. Add few comments to show which code is used on `RN >= 0.52` and which on `RN <= 0.51`.

* Now allowing the custom nav bar to take up the whole space on iOS

The custom nav bar on iOS was really just a custom view applied to the title of the navigation bar.
There were problems with this approach, because the navigation bar messes up the frame of the title very frequently, especially when the orientation is changing. That behaviour is accepted when the title is a label, but not when we have a custom component.

With this pull request the custom nav bar component can take up the full width of the navigation bar, no matter what orientation we're at.

* Added mix of native btns and custom component on the Custom TopBar screen of the example project

The initial modal screen got animated twice, this regression was introduced in #2761.

* custom viewController support

* native component support and e2e

* custom viewController support

* native component support and e2e

* unit test fix

* Rename BottomTabOptionsPresenter

* Set currentTabIndex in BottomTabsPresenter

* implement BottomTabs visible

* options

* proof of concept

* pop

* test fix

* default options

* scale

* rotation

* null check

* refactor

* refactor

* refactoring

* fix tests

* Update TopBar docs (animateHide -> animate)

* Update BottomTabs docs (animateHide -> animate)

* Update Navigation.push docs

* docs/installation-android: remove "@Nullable" annotation

* Docs/SideMenu: Add 'center' prop

* Rename TopBar.animateHide to animate

also fix some options in playground app

* Consolidate topBar visibility in childWillDisappear

* Rename BottomTabs.animateHide to animate

* Added bottomTabFontSize and bottomTabSelectedFontSize properties for android tab bar

* Added tabFontSize and selectedTabFontSize properties to the doc

* Fix default values of bottomTabFontSize and bottomTabSelectedFontSize properties.

For example, the following code will start a single screen app with two
screens pushed into the stack.

```js
Navigation.startSingleScreenApp({
    components: [
    {
      screen: 'example.Types',
      title: 'Navigation Types',
      overrideBackPress: true
    },
    {
      screen: 'example.Types.CustomButtonScreen',
      title: 'Custom Buttons'
    }
  ]
});
```