storing/processing logger names for the API

gonna turn them into functions! or something anyway
renaming the ExecutionEvent to reflect what it really is

going to declare a logger for the document stuff later i think, but for
now it can share
logging is now in the configuration system

yay, runtime changing of the log levels!
prettying up access logging
minor cleanup
registering netty logging

along the way, took out emergency logging configuration because you know
what? TOO BAD. it's always on, that's the point
minimal testing
using the Emergency event as a base class, so that emergencies can all
be handled uniformly if necessary
configuration sketch for app logging
making a controlled way to federate log naming
adding a script console.

this api is not locked in stone, not sure if javascript can handle it.
i'll work it out somehow
have a script console!

this replaces the "print" module, which I will kill off now!
no more print module. use the console now
Merge branch 'feature/logging-configuration' into develop
Merge branch 'develop' of github.com:heinousjay/JibbrJabbr into develop

Conflicts:
	kernel/src/test/java/jj/document/DocumentScriptEnvironmentTest.java