Fix reading resources from command line issue

Now --config.resources./<customFolder> items passed from the command line
are read correctly.
Giving access to the PhantomJS sendEvent method from testing tools.
Fixing an issue introduced by 93411a13cafb165d123a7ec20eeb1333af453102.

Commit 93411a13cafb165d123a7ec20eeb1333af453102 replaced console.log
by window.callPhantom to transmit commands from the web page to
PhantomJS, but there were two places still using console.log.
This commit fixes them.
Changed error message color to bold red

Changed the color to increase readability in Git Bash under Windows.

Close #5.
Configurable number of PhantomJS instances from the includer's package.json

After this commit, one who depends on attester in his "scripts" part of
package.json, can additionally put in that file the following:

 "config":{"phantomjsInstances":2}

to specify the number of PhantomJS instances (instead of passing it via
command line), but as the added benefit, the actual user who npm install'ed
his package, could type:

 npm config set somePackage:phantomjsInstances 8

to take advantage of his multi-core machine.

This setting is taken into account only if there was no
--phantomjs-instances passed from the command line when invoking attester.
Fixing node warnings if >10 instances of PhantomJS launched.

This commit extends commit 0a0d1ac57ecf1e8fbac3e3b2447f8825df1321c9
so that it works even if no --browser is specified on the command line.
Adding a pause/resume link in the status bar.

Fixes #4.