exempt capabilities from error 1006

Added two unit tests.

ArrowSetup errorCheck should exempt capabilities from error 1006 if its
value is null or empty or undefined

ArrowSetup errorCheck should exempt arguments if
config.error1006.exempt is specified
do not modify existing settings if not specified in config string.

Add one more unit test,

ArrowSetup errorCheck should exempt arguments if
config.error1006.exempt is specified but keep other existing exemption
settings if it is not specified in config string

For example, by default capabilities is exempted.
When user only provide a config string which does not modify the
capabilities, the existing exemption settings of capabilities should be
preserved.
Merge pull request #142 from bowdev/null_argument

exempt capabilities from error 1006
Merge pull request #143 from pranavparikh/master

Changing defualtAppSeed url to http, updating verification message for phantomjs startup
Fixing doc.
Fixing doc.
Revert "do not modify existing settings if not specified in config string."

This reverts commit 1b04d1e9f3b63fb5c36d1a72b1be01926e3cef2e.
Revert "exempt capabilities from error 1006"

This reverts commit 5db6d0cdc9d516fd3bbd1ec47bdd2e6af73a6a60.
Only mandatory argument should check null, empty or undefined.

Right now, only seleniumHost is mandatory if it is provided as command
line argument.
Merge pull request #144 from bowdev/null_argument

Null argument
Add in debugCSS to arrow test

Add in debugCSS rules to print to console.  Only useful if you
--logLevel=debug as many of these are simply kind suggestions more then
genuine failures.  Certainly some of these issues are more offensive
than others, but printing to console seems like a safe first step.
Merge pull request #145 from imbrianj/master

Add in debugCSS to arrow test
Merge remote-tracking branch 'upstream/master'
JsLint fix