simplifying the resource cache

no real reason to involve configuration.  at least not yet
making the task name more meaningful
documentation
outdated converter
cleanup
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