introducing http method handlers

basically, the new design of the http server is to take fuller advantage
of netty, by intelligently manipulating the pipeline with specific
handlers for whatever the situation is

moving the handling of individual request methods into different classes
is a natural

along with this is the seed of a new test suite, to help with http
conformance.  it builds a protocol test server that exercises the
complete runtime pipeline with both valid and invalid requests to ensure
that responses are as expected

this is also the first step to driving the event-driven nature of the
server out to the edge.  no more aggregating http objects blindly!  in
particular, methods that can not have a body will get upset and return
an error upon seeing one come in
tiny cleanups

extracted a constant, and set the properties up for background reloading
a LoadedResource is not necessarily a FileResource

it's just a resource that has servable bytes already in memory
added script execution to the RhinoContext
the LessResource

this represents a resource used during rest processing.  it's not a very
capable resource, but it helps to hook into the dependency system for
reloading.

i might try to add a bit to the resource system to make dependencies on
creation of certain paths in pursuit of making this less system smarter
processing css urls in a component

in the old way, this runs as a post-processing step on a CssResource,
which is terrible.  truly terrible.

this is interesting to test, there is some circularity, but it's
working.
goodbye, test for ugly class

soon, goodbye ugly class!
was mocking something for no reason

the resource test system is a mess.  ugly mess.
removing some warnings
refactoring script resource tests

this is in preparation for making the StylesheetResource testable, and in service of removing the old ResourceCreator test hierarchy, which is frankly a load of bullshit
the StylesheetResource

the CssResource has a limited lifespan now.  a quick integration test will ensure everything is A-OK
Integrating the StylesheetResource

also testing it.  there is a small bit of classpath weirdness running the test in eclipse but i feel pretty strongly i'll figure it out
testing the css version of StylesheetResource
fixing asset lookups

multiple paths were not being accomodated, but they are now!
 using the StylesheetResource

the CssResource is gone.  There is some small cleanup remaining.
killing off the LessProcessor

the duties are now taken up by the StylesheetResource, which is much cleaner and fully integrates with the resource system
publishing less events
publishing the less events

changed them around a bit, since they can actually make sense now :D
adding configuration

because hey! the configuration system is now sane and it's fairly easy
to integrate into it
validating LessConfiguration

and some small tweaks to the way the API is set up