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'
    }
  ]
});
```

* basic fab

* fab menu

* fab menu clicks

* pop lifecycle

* options lifecycle

* refactoring

* refactor

* parse unit tests

* refacotr

* fix test

* align

* fab unit tests

* more tests

* size

* hide on scroll in progress

* options

* menu collapse

* parser test

* merge v2

* refactor

* refactor

* more refactor

* more refactor

* fix

* more refactoring

* refactor

* refactor

* fix

* fix

* fixed undefined key

* refactor

* refactor

* refactort

* Refactor resetTo view controller creation into function

This will allow for multiple view controllers to call the same function to create their instance.

* Configure resetTo to take multiple components to set view controllers for

This allows for a navigation stack to be recreated with multiple view controllers rather than just one.

* Breakup view controller initializer into multiple lines for legibility

* Hide topBar with animation by default

* fix unit tests

Closes #2685

* Initial implementation of willAppear and willDisappear

Currently only implemented on pop in StackController

* call clearOptions on super
* TopTabs visible

* fix unit

* generate id only when not already provided

* allows passing id

* fixes #2652

* Set titleBarSubTitleTextCentered as navigator style

- Adapt title center

* fixed false declaration

* applyOptions is applied in correct order

Use custom alert that can be displayed multiple times in quick succession

* Fix Options.copy
* Screens are now by default drawBehind: false

relates to #2711

fixes #2711

* android sdk fix