Make the jettyMaxThreads parameter actually be effective

Calling server.start() before setting a new thread pool caused the new thread
pool to be ignored. Moved the call to server.start() to after the thread pool
has been configured, which now makes the server use the newly configured thread
pool instead of the default one.

Fixes "Selenium grid Jetty server thread count cannot be configured by
parameter jettyMaxThreads":

	https://code.google.com/p/selenium/issues/detail?id=7240

Signed-off-by: Andreas Tolfsen <ato@mozilla.com>
Add Alex Henrie and Robin Stocker to AUTHORS
Use LogLevelMapping to convert JSON wire protocol name to Level instance.

Without this, the java bindings fail to parse the "DEBUG" log level,
which is valid in JSON wire protocol but not a recognized Java log level
name.
Clean up internal Firefox logging API.

* Removed redundant code
* Use named loggers so it's easier to find log message origins
Add explicit API for configuring log prefs rather than forcing users to rely on
magic capability strings.
Catch driver start-up failures.
Merge remote-tracking branch 'origin/master' into msft
Updating name of getCookie command
Updating .NET bindings cookie serialization to omit non-specified optional fields