bin: use `stdio: 'inherit'` for child process spawn

Fixes deprecation warning in node v0.11.x:

  child_process: customFds option is deprecated, use stdio instead.
resolves #1066: generate better async trace if done() is called multiple times
update .editorconfig to respect trailing whitespace in markdown files
Merge pull request #1337 from boneskull/mocha-1066

resolves #1066: generate better async trace if done() is called multiple times
#1190: add error message to failed test with json-stream reporter
visionmedia->mochajs

Partly fixes #1397.
Merge pull request #1398 from cscott/patch-1

visionmedia->mochajs
updating package.json, bower.json, component.json for new repo url
tryna fix failed build
update links to site
Merge pull request #1391 from TooTallNate/fix/v0.11.x-deprecation-warning

bin: use `stdio: 'inherit'` for child process spawn
Release 2.0.0
rebuild & bump to 2.0.1
update maintainers and contributors
Fail when test resolution method is overspecified

Users may register `Runnable`s as asynchronous in one of two ways:

- Via callback (by defining the body function to have an arity of one)
- Via promise (by returning a Promise object from the body function)

When both a callback function is specified *and* a Promise object is
returned, the `Runnable`'s resolution condition is ambiguous.
Practically speaking, users are most likely to make this mistake as they
transition between asynchronous styles.

Currently, Mocha silently prefers the callback amd ignores the Promise
object. Update the implementation of the `Runnable` class to fail
immediately when the test resolution method is over-specified in this
way.