Move to use local authorize-ios

[imurchie]

Proposed changes

authorize-ios has been moved into appium-ios-driver, the only place where it is needed. Now wire that into appium so it is exposed as a global executable, and update the documentation to remove the requirement to install the external package.

Global binaries installed:

→ ls -la /Users/isaac/.nvm/versions/node/v11.3.0/bin
total 39872
drwxr-xr-x 7 isaac staff      224 Jan 15 11:41 .
drwxr-xr-x 9 isaac staff      288 Jan 15 11:40 ..
lrwxr-xr-x 1 isaac staff       44 Jan 15 11:41 appium -> ../lib/node_modules/appium/build/lib/main.js
lrwxr-xr-x 1 isaac staff       58 Jan 15 11:41 authorize-ios -> ../lib/node_modules/appium/node_modules/.bin/authorize-ios
-rwxr-xr-x 1 isaac staff 40825008 Nov 27 00:17 node
lrwxr-xr-x 1 isaac staff       38 Nov 27 00:17 npm -> ../lib/node_modules/npm/bin/npm-cli.js
lrwxr-xr-x 1 isaac staff       38 Nov 27 00:17 npx -> ../lib/node_modules/npm/bin/npx-cli.js

This also exposes an npm script to do the same, for use in local installations from source.

See #7475

Types of changes

What types of changes does your code introduce to Appium?
Put an x in the boxes that apply

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

• I have read the CONTRIBUTING doc
• I have signed the CLA
• Lint and unit tests pass locally with my changes
• I have added tests that prove my fix is effective or that my feature works
• I have added necessary documentation (if appropriate)
• Any dependent changes have been merged and published in downstream modules

[mykola-mokhnach]

wow, you know Chinese