Silence gradle deprecation warnings in v6

[chrisinmtown]

Declare dependencies with implementation, drop deprecated compilation
Refactor dependencies from the two submodules into parent
Upgrade com.moowork.node plugin to version 1.3.1
Upgrade node/npm to version 6.14.4
One deprecation warning remains about NpmSetupTask:
Property 'args' is not annotated with an input or output annotation

[chrisinmtown]

I can barely spell gradle, I'm definitely not an expert, please check this carefully.

[holmari]

I couldn't test it aside from the fact that it compiles, but it looks good aside from having some potentially extra deps for all projects.

[holmari]

Can we keep the added dependencies where they were before? Not all of the projects need to depend on every library.

Separately, if we want to declare the list of dependencies in just one place so we can make sure that each module is using the same version, we could do

ext.libs = [
  guava: 'com.google.guava:guava:18.0',
  ...
]

in this file, and then in other build.gradle files, we could refer to that by saying implementation libs.guava or something of that sort.

[chrisinmtown]

Please make any change you like to this PR, it was just a first draft.

[holmari]

@chrisinmtown since you were wondering about the GitHub etiquette elsewhere; the author tends to 'own' their own PRs in most projects I've worked on. I hope this doesn't dampen your enthusiasm, it's great to see these PRs coming from you! 👍

[chrisinmtown]

Thanks yeah I get it :) but gradle is black magic to me so I'm hoping maybe you'll make the fine adjustments and I'll learn from that.

Instead of fighting gradle, I'm focusing on extending this tool for HTTPS with as little disruption as possible to existing code.