unfortunately, it doesn't list full path to dependency files, so is
useless for determining other projects that deps came from.  Committing
purely so have record of how to do this should I come back to it.

also do some cleanup for task generation

The gradle APIs that use resolved items will be deprecated eventually.
so best not to use them.  This also reduces memory overhead.

Gradle task validation would fail if the directory already existed with
the other annotation.

the classpath configuration has "runtime" varients for artifacts that
allow it to look at classes directories rather than jars.  This avoids
errors because project-dependencies may not always have jars generated.

Now generates a stub output file so that downstream tasks don't bomb.

Looks like ABSOLUTE is relative to the root project

will merge in Analyzer to the task to avoid duplication

correct for bug where jdeps doesn't report dependency if referenced
class in same package as current class, even if it's in a different
module.