Turns out the popping a screen while keyboard is
open has no side effects. The issue was in fact
that under some condition, when adding a screen
back after it was previously removed caused the
screens constructor to be called.

This commits prevent startReactApplication from
being called by setting mAttachScheduled flag.

This commit includes two major changes

1. Move all calls to private react-native API to a single class and
change access modifier of the ReactRootView to private.

2. Hide soft keyboard when a view is removed from screen. This
potentially fixes a bug we encountered internally where react
failed to render the shadow DOM properly, when popping a screen
while the soft keyboard was displayed.

Android drawer implementation

Android style fixes

Fix Android example

Add Android installation instruction

Should consider a better approach

When starting new activity after previous activity showed modals
and did not dismiss them. The modal controller still had
registered modals even though we can't go back in the activity stack.

* Use navBarButtonColor to tint Toolbar instead of buttonsTint

* Use navBarTextColor to tint Toolbar instead of titleColor

Since Toolbar icons' height is set according to Toolbar height,
We need to ensure the call to `setupToolbar` from `onCreate` is
called after the Toolbar is measured.

navigatorEventID was generated from navigator, probably by mistake.
This caused a bug which was noticeable when showing modals from
a pushed screen. In this case two components shared the same
navigatorEventID thus they both responded to events from native.