Mocha constructor: improve browser setup

[juergba]

Description

The browser setup can result in an error when the option and its corresponding function don't match in their name, eg. --diff<==> hideDiff().
see comment

Mocha options are used in different contexts:

• via CLI: options can be set with canonical / alias / camel-cased canonical / camel-cased alias names.
  The parser autocompletes the names and the whole bunch of options is dumped into the mocha instance.
  eg. --timeout 200 results in: {timeout: 200, t: 200 timeouts: 200}

• using Mocha programmatically: Mocha constructor accepts and processes only canonical or their camel-cased option names,
  eg. {timeout: 200, checkLeaks: true}

• browser: setup() calls public function where option name matches function name.

mocha.setup({
  global: ['foo']  // calls Mocha#global()
});
mocha.checkLeaks(false);  // should work also with 'false'

Description of the Change

• Following public functions are also used for the browser setup. Currently they are just able to turn the feature on (true). They should work both ways (true or false):
  • Mocha#allowUncaught
  • Mocha#asyncOnly
  • Mocha#checkLeaks
  • Mocha#forbidOnly
  • Mocha#forbidPending
  • Mocha#fullTrace
• Mocha#ignoreLeaks: soft deprecate (Mocha#checkLeaks already exists)
• Mocha#globals: keep this function, since its an alias name and add a new Mocha#global
• Mocha#hideDiff: soft deprecate and add a new Mocha#diff
• Mocha#useColors: soft deprecate and add a new Mocha#color
• Mocha#useInlineDiffs: soft deprecate and add a new Mocha#inlineDiffs
• fix some JSDoc links

[coveralls]

Coverage increased (+0.03%) to 92.74% when pulling f50cb95 on juergba/mocha-browser into f73e7c6 on master.

[craigtaub]

Nice 👍 . Anything to standardise the usage is good in my books.