It was added by mistake to the library’s manifest instead of the e2e application’s manifest.

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.

Closes #681

* [android] Basic implementation of orientation change event and getter

#dasdsa

* [android] Check if fabAnimator is not null

* [android] Add configChanges prop to NavigationActivity in AndroidManifest

* [android] Fix duplicate declaration of onConfigurationChange

* [android] Use EventEmitter class to dispatch orientation change events

Ignore config changes in portrait and landscape activities

* Landscape only option

* Fixed typo

* Removed old startApp

* Spacing

Adds BottomTabActivity which replaces TabActivity
Adds a dependency on `com.aurelhubert:ahbottomnavigation:1.2.3`
Uses iOS tabsStyle, with additional parameter that allows toggling of whether to show the titles of inactive tabs

Navigator.push allows us to open a new screen. Currently it starts a new Activity with the screen
as it’s root view, but this is only a temporary behaviour. The intended behaviour is similar to
View Controllers on iOS which allows you to manage view hierarchies or a stack of fragments
managed by FragmentManager on Android.

The approach we took is fairly simple. Navigation is created natively in corresponding activity,
currently only TabActivity is supported, and we pass the styling parameters and screenId to it.
Each screen is rendered in its own ReactRootView and is wired to the same ReactInstanceManager,
so all screens share the same java script context.