Should enable merge settings to be shown during initRepo

Now no need to detect at onboarding time. Also suggests removing setting in migration if it is already the same value.

Closes #528

No need for {{semanticPrefix}} to be specified in templates now - it will be implicitly added to start of commit message and PR titles if semanticCommits=true

Links to open issue about workspaces.

Closes #601

Checks for legacy PR title format so we don't accidentally recreate any of those.

Now will use “v1.0.0” instead of “version 1.0.0”

Closes #587

This allows for the easy overriding of our default `renovate/` branch naming.

Closes #586

Adds a zero width space between the # and first digit in issue numbers to prevent GitHub autolinking, also replaces escaped backticks with `<code></code>`

Closes #595

commitMessage and prTitle will be converted to lowercase after compilation if semanticCommits=true

Fixes #594

Closes #226 

- Renames `packages` to `packageRules`
- Refactor `packageName` to `packageNames` array
- Refactor `packagePattern` to `packagePatterns` array
- Adds `excludePackageNames` array
- Adds `excludePackagePatterns` array

Closes #529

Massaging of string to array is done in migration function.

depTypes configuration is now refactored from being an array of strings/objects to having each type of dep (`dependencies`, `devDependencies`, `optionalDependencies`, `peerDependencies`) be a first class object in the namespace. The "old" way of configuring is still supported but is transformed using a migrateConfig script. Later, PRs will be raised to impacted repositories to suggest the new config.

This PR adds explicit patch support. A user can set `separatePatchReleases` to true and receive not only major/minor updates but also patch updates separately. This functionality is also implicitly enabled if `automerge` is set to `patch`.
This PR also enables separate major/minor/patch configuration, e.g. config overrides for major versions, for patch versions, etc. `branchName` is currently overridden for patch branches using this technique.

Closes #390, Closes #538 

Escape all scoped package mentions
Escape in group PR bodies too
Remove empty repositoryUrl links

GitHub attempts to autolink any @user mention and this causes problems when we use scoped npm modules like `@types/gulp`. This escapes such package names with a zero width space to fool GitHub’s parser.

Fixes #518

Usernames can now be expressed as like either ‘rarkins’ or ‘@rarkins’

Closes #564

* chore(deps): Update lock file

* chore(deps): Update lock file

This feature is particularly useful in the case that renovate is enabled on all repositories a user/account has. Many of those might be forks, and it makes no sense to renovate those by default. Instead, Renovate will skip over forked repositories unless a renovate.json has been added to their root.
Also, Renovate will now prune branches after deciding to skip a repository, whether because of a fork or disablement.

Closes #541

The GitHub API will now retry up to 3 times before giving up, if it is receiving a 502 Bad Gateway response.