fix(config): Separate ENOENT error handler from others

This prevents karma from incorrectly reporting a config file not found error in the case where the code inside the config file throws an ENOENT error for other reasons

style(config): indentation, error messages

Fix indentation mistake, improve error message, add process.exit(1)

test(config): add missing test

to ensure proper error reporting when a config file throws an ENOENT error of its own

style(config): whitespace and var scope

Removed trailing whitespace and moved configSrc declaration outside of the try/catch block
Merge pull request #465 from ashaffer/patch-1

Fix incorrect config file error message in some cases
docs: little tweaks
docs: add a page about Semaphore CI
chore: add init-dev-env for easy workspace setup
chore: move non grunt scripts to scripts
chore: refactor the init script a bit
chore: remove log4js install hack

Since 0.6.3, log4js works on both 0.8 and 0.10 so we don't have to do this hack anymore...
https://github.com/nomiddlename/log4js-node/issues/129
feat: allow inlined plugins

plugins = [
  'npm-module-plugin', {
  'launcher:inlinedLauncher': ['factory', ...]
];
fix: better error reporting when loading plugins
chore: update contributors
chore: release v0.9.2
chore: don't create the symlink from node_modules

Let nom to install another copy of karma. This symlink only causes troubles. (eg. npm link or npm install on linux will get into recursion install of karma)