refactor(config): junit/coverage plugin configs

This stuff belongs to these plugins:
https://github.com/karma-runner/karma-coverage/commit/2ac2f71a1af13ff40674b4884173b6b487bf4f19
https://github.com/karma-runner/karma-junit-reporter/commit/ff21972c735f160e66085f8fedaa81c8efbb0e0f
refactor(config): remove the BC warnings
refactor(config): extract normalizeUrlRoot
fix(config): use polling by default

This should have been set to `true` in 18514d63534c82094b231eb1e0b0e41011519183. It's reversed.
test(e2e): fix typo in a comment
chore(deps): use HTTPS for fetching npm modules

This stops npm from erroring with useful messages like this:

    npm ERR! git clone git://github.com/karma-runner/karma-coverage Cloning into bare repository '/home/fidian/.npm/_git-remotes/git-github-com-karma-runner-karma-coverage-f5a5ab06'...
    npm ERR! git clone git://github.com/karma-runner/karma-coverage
    npm ERR! git clone git://github.com/karma-runner/karma-coverage fatal: unable to connect to github.com:
    npm ERR! git clone git://github.com/karma-runner/karma-coverage github.com[0: 192.30.252.129]: errno=Connection refused

and like this

	npm ERR! not a package /home/fidian/tmp/npm-17172/1382734998255-0.33902470069006085/tmp.tgz
	npm ERR! Error: ENOENT, open '/home/fidian/tmp/npm-17172/1382734998255-0.33902470069006085/package/package.json'
fix(proxy): handle proxied socket.io websocket transport upgrade

Fixes websocket upgrade handling for proxied routes.
This was motivated by long (10s) default timeouts when socket.io
attempts to use websockets and fails to perform the upgrade.
Merge pull request #815 from Demeterr/fix-websocket-proxy-better

fix(proxy): handle proxied socket.io websocket transport upgrade
docs(config): preprocessor transformation clarification

- Pirmary motivation to clear up confusion around how to reference .html files per html2js preprocessor.

Clsoes #788
chore: update contributors
chore: release v0.11.2
Merge pull request #816 from jfroom/docs-preprocessors

docs(config): preprocessor transformation clarification
docs(contributing): add missing links
chore: update contributing guide
chore(init-dev-env): add a copy of rimraf to make it simpler

Adding a copy of rimraf, so that people don't have to install it before running `./scripts/init-dev-env.js`.
docs(contributing): remove the note about grunt 0.4

Nobody uses grunt 0.3 anymore...
docs(plugins): fix a broken link
fix(config): not append empty module if no custom launcher/rep/prep

Just to get rid off the confusing debug message:
"DEBUG [plugin]: Loading inlined plugin (defining )."
feat: remove `karma` binary in favor of karma-cli

BREAKING CHANGE:
The `karma` module does not export `karma` binary anymore. The recommended way is to have local modules (karma and all the plugins that your project needs) stored in your `package.json`. You can run that particular Karma by `./node_modules/karma/bin/karma`. Or you can have `karma-cli` installed globally on your system, which enables you to use the `karma` command.

The global `karma` command (installed by `karma-cli`) does look for local version of Karma (including parent directories) first and fall backs to a global one.

The `bin/karma` binary does not look for any other instances of Karma and just runs the one that it belongs to.
feat(config): log if no config file is specified

Now that Karma tries to be a bit more clever and tries `karma.conf.js` or `karma.conf.coffee`, it's helpful to know that no config file was loaded.