Static code analysis using PMD

[zod]

Opening files with IntelliJ IDEA shows a lot of warnings for our code. This is distracting and makes it hard to see new warnings being added.

PMD and the gradle plugin allow automatic code checks during build (and CI) to prevent new violations from being added.

I've enabled the quickstart ruleset and initially disabled all rules which are currently violated. Re-enabled (and fixed) rules are:

• AvoidInstanceofChecksInCatchClause
• LogicInversion
• LooseCoupling
• SimplifiableTestAssertion
• SimplifiedTernary
• SimplifyBooleanReturns
• SingularField
• UnnecessaryFullyQualifiedName
• UnnecessaryImport
• UnnecessaryModifier
• UnnecessaryReturn

Each rule is a single commit and can be removed I it's deemed to strict.

[afischerdev]

Fine helper.
But before we merge this please merge all pending PRs that have no conflicts.

• Update lib part one - interface #478 and Add test profiles with lookups.dat #481
• Test voiceHints #456 could be closed, I already have a test based on the same logic as in Tests for RouteServer #474. I add it later.
• Update lookups #458 can wait, needs a decision
• Add generation URL in GPX export #188 I could add when I come in lib update on that passage
• Determine version from git tags #457 is draft

[zod]

I'm not sure why the other PRs are a prerequisite to this PR but I've either merged, commented or closes those PRs.

If this PR is merged those PRs that are still open should merge the master to get the ability to run all checks locally instead of getting feedback just from the CI build.