Fix: modularize

[cstamas]

Modularize with overhauled dependencies.

Changes:

• added module-info.java
• deps updated (and also modularized)
• locked down the whole build
• Toolbox stats: https://gist.github.com/cstamas/4539094ce7be5327b0ca0b117211a600

From now on, to update anything in the build (any plugin or dependency) one needs to maintain checksums as well: one can do it by using -Daether.artifactResolver.postProcessor.trustedChecksums.record user property in a trusted environment. Then immediately validating in some independent env (like CI is -- build should pass, otherwise trusted environment is compromised).

[cstamas]

java-ipfs-http-client is the only project having module name != package name. Do we want to change anything about it?

[ianopolous]

I'll leave this up to you.

[cstamas]

I'd align those, but TBH am not happy with package name either, is too generic: io.ips.api does not include neither protocol (HTTP) neither any other designator that could make it differentiate from any other "api-like libraries". But IMO aligning to Java package should be ok.

[cstamas]

Aligned them.

[cstamas]

Locked down whole build. Build will fail if any used artifacts (build related, like plugin or dependency) changes or being messed with: sha512 checksum mismatches or artifact has no sha512 enlisted here.

[cstamas]

From now on, if anything is changing (on purpose), checksums needs adjusting. It can happen manually (tedious but works), or it can be updated "in bulk": in trusted environment rebuild with added -Daether.artifactResolver.postProcessor.trustedChecksums.record user property (and when checking in changes watch for .bak files, to not add them). Next, immediately validate changes on unrelated environment (like CI)

[cstamas]

The stats with PR:
https://gist.github.com/cstamas/4539094ce7be5327b0ca0b117211a600

[cstamas]

Ready for merge.