fix(coverage): always send a result object

This is just a fix for stable, in the master I will change the implementation,
so that the "testacular" is responsible for sending the coverage results, 
rather than individual adapters.

Closes #365
fix(config): do not change urlRoot even if proxied

This basically reverts 8b4fd64df6b7d07b5479e43dcd8cd2aa5e1efc9c
See https://github.com/testacular/testacular/commit/8b4fd64df6b7d07b5479e43dcd8cd2aa5e1efc9c
fix(reporter.teamcity): report spec names and proper browser name

Applying https://github.com/testacular/testacular-teamcity-reporter/commit/824188e96abfde75bb74ac6238b6e708ce2b82c6
chore: Update grunt and grunt-simple-mocha for 0.10
chore: Update mocha to 1.8.2.
refactor(config): Make path.resolve node 0.10 compatible.
Test for undefined when passing arguments to path.resolve as
node will throw an error since 0.10 otherwise.
chore: Update .travis.yml to include node 0.10
chore: Trigger travis build.
chore: release v0.6.1
chore: rename this shit to Karma

BREAKING CHANGE: this breaks in couple of ways
- whenever you call the "testacular" binary, change it to "karma", eg. `testacular start` becomes `karma start`.
- if you rely on default name of the config file, change it to `karma.conf.js`.
- if you access `__testacular__` object in the client code, change it to `__karma__`, eg. `window.__testacular__.files` becomes `window.__karma__.files`.
chore: set node dependency to a fixed version (0.8, 0.10)
chore: update contributors
chore: release v0.8.0
chore: change twitter to @JsKarma
fix(runner): send exit code as string

Closes #403
fix(init): fix for failing "testacular init" on Windows
chore: update http-proxy del (compatible with Node.js 0.10)
fix(preprocessor): resolve relative patterns to basePath

Merged from master to stable.

Closes #382

Conflicts:
	lib/config.js
	test/unit/config.spec.coffee
test(e2e): remove **/ prefix from coverage

As it should not be required anymore...
chore: update contributors