Enable Java build and configure sensitive logging

Building Java application failed if no "org.jetbrains:annotations:jar" of version 7.0.2 was in local Maven cache.
Change reactor pom to fix injected (through parent) dependency version to publicly available version 13.0.

Logging was set to "TRACE" for "com.lyndir" which logs master password to console / STDOUT.
This is a sensitive information and it's uncertain if STDOUT might not be captured and logged to system logging in some environments.
Therefore it's better to not log TRACE level information per default.
To keep flexibility (e.g. for testing) a system property named "masterpassword.loglevel" can be defined at startup command line and it's value will be used as log level, instead of default "INFO".

Logging (logback) was set to scan configuration file for changes and reconfigure log environment.
In normal usage execution is from within a JAR, so log file cannot be changed at runtime.
Nevertheless logback tried to set up a change listener and failed, which was logged as an error.
To prevent further misleading error logs "scan" was disabled, as it's useless nevertheless (most the times).