py-logging: added logging to java_runner

- Along with importing the logging module, we initalize a global logger
  that has the same name as the util.java_runner module. Then we add a
  null handler so that the log message will go nowhere if the
  application doesn't add a better handler.
- Added some preliminary debug logging to the java_runner.  No real
  cases for info/warn needed yet. (Eventually, we should detect if
  stderr from the java process is non-empty, and print it with a
  warning instead of debug.)
py-logging: added logging to GGPServerProcess.
py-logging: added logging to dispatch.dispatchServer, including replacing a print with a logging.debug
py-logging: added logging to worker.ggpPlayerProcess, only one debug call.
py-logging: Added logging to worker.workerServer.
py-logging: added util.logging_help...

Because the goal is to use the logging config files, we don't get to
touch the logging handlers, because they're constructed for us.  So the
only way to get to the handlers to adjust only them is to examine the
loggers' __dict__ fields, pull out their handlers, and adjust them.
- One function sets the level of all StreamHandlers, so that we can
  adjust debug/verbose/quiet modes for the program, while leaving the
  file logs at debug level.
- One function resets the file that is used by a FileHandler, so that we
  can have log files named after the ports that are read as commandline
  arguments.
py-logging: added config files for dispatcher and worker.
py-logging: added logging to run{Dispatch,Worker}.py scripts...

- Uses config file logging.d.conf, logging.w.conf
- Takes -d/--debug, and sets logging of console level to DEBUG if seen
- Takes -v/--verbose and sets logging of console level to INFO if seen
- Default console log level is WARN
Merge branch 'py-logging' into develop--Finished adding logging.