adding the ConfigurationScriptEnvironment

it doesn't do much yet, but the system recognizes and executes it
refactoring the location

the bundle just makes more sense in the interface,
the whole world can use it
introducing the seed of the configuration API
need a place to collect the config values

the idea is that we really just have a map that represents the values
that get set by the configuration script, and the entire set of
configuration values gets updated atomically for the sake of the rest of
the system.

code-gen to read things out might get weird.  not sure yet, javassist
sometimes gets caught up on generics
using the ClassPoolHelper

this class is about to be replaced
the new configuration system begins in earnest
removing a warning
new implementation of config objects

different sort of code gen going on now, instead of trying to create a
function for the config script automatically, there's just a simple bus
to carry the info, an API to make it simple to construct config API
objects, and a few other attendant refactorings
reworking the http binding
configure http bindings the new way
moving the new events to their own files
removing an unused import
a provider for config objects

i'm not sure if this implementation will survive, but it's definitely a
simple way to handle things. register the config object binding, and
inject it.  voila.
some objects moved
pointless cleaning up a space
object moved
publishing configuration events
testing the configuration events
externalizing http argument reading
adding enum conversion

no real reason for this. i just decided to see if it would work and it
does. this could certainly come in handy for configuration