Name already in use

Closes #1696

Also reorganized npm scripts.

Also removed it from published files, since the script doesn't seem to be used.

Fourth part of reorganizing and cleaning up test-folders.

Third part of reorganizing and cleaning up test-folders.

Second part of reorganizing and cleaning up test-folders.

First part of reorganizing and cleaning up test-folders.

Also changed protocol to https.

Resolves handlebars-lang/docs#70

This site is served via HTTPS and provides the latest
Handlebars.js versions.

This was found by running an IntellijIDE
code inspection for proofreading.

If `global` is used and handlebars is compiled for browser
usage without a Node.js `global` polyfill, handlebars
fails with a `global is undefined` error.

Fixes #1593

Also updated all URLs

...to point to 'https://mustache.github.io/...'

# Conflicts:
#	components/bower.json
#	components/handlebars.js.nuspec
#	components/package.json
#	integration-testing/multi-nodejs-test/test.sh
#	package-lock.json
#	package.json

The SauceLabs IE setup has problems and does not work
with the endpoints that we use to run them. This is a Saucelabs problem, but it has been there for a year now. Until we use another API, I will simply remove the browsers

somehow the variable "$i" gets overwritten in integration-testing/multi-nodejs-test/test.sh:20, which is why we now rename it to a more meaningful variable

Extracts the parser to `@handlebars/parser`, where it can be shared
between different implementations. This means that e.g. Glimmer/Ember
will be able to iterate on new features without forcing Handlebars to
adopt them immediately, and vice versa. All implementors will be able to
absorb changes as it makes sense for them.

The project was moved, but some links weren't updated accordingly.

# Conflicts:
#	integration-testing/multi-nodejs-test/test.sh
#	spec/string-params.js
#	spec/subexpressions.js
#	spec/track-ids.js

#1683)