Refactored tests to use wd promise-chain api
support selendroid 4.4/19 better
fix selendroid app launch issues
require a dot for a relative activity, otherwise we consider it a full one
Fix issue #1713: Change killProc signal from SIGKILL to SIGTERM.
switch values at assertEquals statements, to reflect the correct meaning
kill chromedriver before starting new chromedriver
add bitdeli tracking
Fix android multiple devices: android/android-common.js
native instruments configurable as capabilities
Support full-reset for selendroid

Replay commit ad9c73a3c45cfa8352dac2e5b7943a19b615b14b
Return accessibilityHint as element's attribute 'hint'
windows compat fix in android binary finding logic (attempt to fix #1759)
Implementing mobile:background command for Android and Selendroid

Replay commit 1c6b495cd2f3fbbb8622a9fb43f3e50aa79ab82e

Remove debug log

Tidy up spaces according to pull request review

Fixed indentation according to Appium project style guide (2 spaces indent)

Fixed error management in background method

Add an argument to ADB.startApp in order to choose whether to stop the app prior to starting it

Conflicts:
	lib/devices/android/adb.js

Refactored mobile:background method for Android: using ADB.startApp rather than directly issuing am start command to ADB shell, do not return to callback until app is back to foreground

Mimick the launcher start intent for the app when starting it

The Android launcher uses the following settings to start apps:
- MAIN action
- LAUNCHER category
- FLAG_ACTIVITY_NEW_TASK
- FLAG_ACTIVITY_RESET_TASK_IF_NEEDED
Without those settings there were discrepancies between Selendroid and
Android when trying to bring the app back to foreground: it would not
bring back the existing Activity stack but create new activities

Adapt background code to new startApp signature

Added "retry" argument

Missing space

Spaces after if

Fixed spacing issue

Split long line
Added doc for nativeInstrumentsLib cap
use a messy loop instead of a deeply nested async fn chain (fix #1523)
add test for app backgrounding to android/selendroid
make ios tests a bit more robust
fix test, this is what i get for using another editor
reverse test assumption (cc @sebv)
changelog and bump to 0.14.0 for publish