This reverts commit 514d527d.

Adds a new `rangeStrategy` value `lockfile-update'. Enabling this means you will get PRs that contain updates for the versions in your lock file (currently npm and yarn only) even if the range in the `package.json` file hasn't changed because the update is "in range".

Closes #1382 

Automerge branch even if PR has previously been raised, so long as only one commit exists. This handles the case where an initial update e.g. v1.0.1 fails, causing PR to be raised, but then a v1.0.2 is published which fixes the failure.

Closes #1381

Rename all VSTS references to be Azure DevOps.

Closes #2810

BREAKING CHANGE: 'vsts' platform is now renamed to 'azure'

Deprecate use of “special” env var like `GITHUB_TOKEN` and instead standardize on `RENOVATE_*` environment variables instead.

Closes #2834

BREAKING CHANGE: For GitHub, GitLab, Bitbucket and VSTS you need to migrate `*_ENDPOINT` to `RENOVATE_ENDPOINT`, `*_TOKEN` to `RENOVATE_TOKEN`, and same for `BITBUCKET_USERNAME` and `BITBUCKET_PASSWORD`.

Closes #3096

Catches an edge case where a PR is configured for automerge and a new update comes right before automerge. If branch protection wasn’t configured, Renovate was using a “stale” branch status to think it’s OK to merge. Added an additional check before automerging that should catch it.

Fixes #3099

Closes #3088

This reverts commit 625fa474.

Needed for package managers that support more than one depType (e.g. Bundler).

Closes #3076

Closes #3078

Closes #3082