Add dependency management for each auto project independently vs relying on transitivity

Auto are being good libraries by shading their internal use of guava.

https://github.com/google/auto/pull/160

I noticed that there's no longer a transitive dep on auto-service from auto-value anymore. Let's call these out independently
> I'd rather not add it by default

TL;DR: +1 to that. Unless we get feedback that copy-pasting a couple of deps is so annoying that we need to avoid the need for it, I'd rather keep our user impact down by keeping the list of transitive deps as small as possible.

The set of dependencies that we propagate to all modules that inherit from jclouds-project should be as small as possible. I agree with @jdaggett that we want to use `Auto*` wherever possible, but putting the deps in `<dependency>` doesn't enforce that anyway, and copy-pasting a couple of deps when creating a POM doesn't seem like a huge overhead at this point (certainly not when compared to the overall size of our POMs...but that's another discussion ;-) )