new "dist" module to create a single final ehcache jar artifact

Not sure how we want to do this really. I guess it makes sense for the 107 stuff to be in this uber jar. But I don't think we want the 107-api (the spec) to be a runtime dependency, but it should probably be provided. Do we need to do anything for that? Or am I just wrong? The rationale is this:
 - We want people that want to use Ehcache w/o 107 to be able to do w/o the extra dep.
 - In EE environment it (eventually) be an issue and people will need to exclude the dep (which, if they don't use 107 in that environment, will be even more awkward).