When updating a tab icon, if null was used as color - it would get applied.

Add docs for bottomTab requiring icon on Android

This new updateProps command allows to update props for a component registered with Navigation.registerComponent.
The updated props are handled by shouldComponentUpdate and componentDidUpdate lifecycle methods.
This commit builds upon the work done in 291f16177d and is a breaking change.

Add support for NavigationBar color on Android

This commit adds support to update props of screen or custom button/title via the mergeOptions api.

```js
Navigation.mergeOptions('myComponentId', {
  passProps: {
    text: 'new value'
  }
});
```

Fix topBar title alignment

Until now, mergeOptions would merge with parent controller only if mergeOptions was called with
a componentId. This commit fixes the issue and makes options merge correctly even when called with a layoutId.

* Sets the window background color to the system's one for dark mode support

* Fix title layouting on iOS 13

For some reason it returned cyan... probably leftover from a debug session

* Use iPhone 11 in detox e2e

* Run detox e2e tests on iPhone 11

* Run detox e2e tests on iPhone 11

* Upgrade detox@14.x.x

* Exclude broken e2e test on iOS 13

* Add fontWeight support on iOS

* Add tests

* Fix tests

Add support for getLaunchArgs on Android

**Usage:** 

1. **Pass** args in order to run the application on the device using ADB or xcrun or Detox:
    - Detox: `device.launchApp(bundleId,{launchArgs: {'-key1': 'val1'}})` must use launchArgs key, see [docs](https://github.com/wix/Detox/blob/master/docs/APIRef.DeviceObjectAPI.md#7-additional-launch-arguments).
   - ADB: `adb shell am start -n com.yourpackage/com.yourpackage.YourActivity --es launchArgs "{some stringyfied json}"`
   - Xcrun: `/usr/bin/xcrun simctl launch ${udid} ${bundleId} --args -key1 value1 -key2 value2`

2. **Retrieve** the arguments: `const launchArgs = await Navigation.getLaunchArgs();`
   - There is a small difference between platforms on how they pass the launch args:
       - on iOS, the args will be passed as an array of pairs (argv,argc)
       - on Android, the args will be passed in the form of a dictionary 


Extract args as a dictionary example:
```javascript
const launchArgs = await Navigation.getLaunchArgs();
let resultArgs = {};
    if (Platform.OS === 'android') {
      resultArgs = launchArgs; // no need to proccess its a dictionary 
    } else {
      for (let i = 0; i < launchArgs.length; i += 2) {
        if (i + 1 < launchArgs.length) {
          resultArgs[launchArgs[i]] = launchArgs[i + 1];
        }
      }
    }
```

Improved stack and Sidemenu docs

With this change, dynamic colors will be supported when tinting an image and the image color will change on the fly depending on the dynamic provider and traits. This will be especially useful when supporting the new dark mode in iOS 13.

Apparently lockMode conflicts with visibility - If a menu is visible and lockMode locked is applied the menu closes.
Also removed temp code related to workaround introduced for temp sideMenu options (visibility)

This change ensures that the visibility option is applied only once.

Fixes #5444

FIx SideMenu options not being merged correctly with other options.

* Fix button with react component doesn't get unmounted

* Test e2e only on iOS

Break all the PRs :(

iOS and Android code base used different naming conventions - this commit aims to unify naming conventions. I probably missed a few properties here and there so this will be an ongoing effort.

There is no need to call `setDefaultOptions` on the `childViewController` while iterating the `childViewControllers` as those will be passed recursively as `rootViewController` anyway and thus calling `setDefaultOptions` in the nested recursive call.

When setRoot is called with `waitForRender=true`, check if the root view is destroyed before displaying it.

* Don't cache values for constants() call

The reason we can not cache the values is because the implementation differs per OS. Android returns static values while iOS will actually crawl the layout and return it's heights. The caching mechanism here meant that iOS would only return the heights of the layout it calculated the first time.

* Update docs regarding inconsistencies in Constants