DatabaseShutdownRollbackTest: Fix false unit test failure

- Symptom would be JUnit failing with "Test class should have exactly
one public constructor" about the Leak and Thing member classes.
- Reason is that JUnit will consider member classes of test classes as
test classes themselves, but they were not meant as such in this test.
They are merely helpers for their parent class.
- I did not notice this when committing the tests because it only
happens with the ant test runner, not with the Eclipse one. Sorry.
- Notice: The tests will still fail due to
test_WillAlwaysFail(DatabaseShutdownRollbackTest.java:66) failing with
a regular test failure (AssertionError). This is intentional breakage
to force developers to fix the following issue before deploying a new
build: https://bugs.freenetproject.org/view.php?id=6247. It is
specified at the class level JavaDoc of the affected test already.
DatabaseShutdownRollbackTest: Disable always failing test because the
underlying issue was postponed

- The test was specifically added to enforce fixing of
https://bugs.freenetproject.org/view.php?id=6247 before deploying the
next build. (This is also specified at its class-level JavaDoc)
- It was decided to postpone the issue to WOT 0.4.2, so I am disabling
the always failing test now.
Merge branch 'master' of https://github.com/freenet/plugin-WoT-staging
Merge remote-tracking branch 'origin/master' into use-plugin-fcp-rewrite
Ant builder: Explain why we put *.txt into the JAR

I've searched the affected directory for *.txt and the only file is
gpl.txt. So thats what it probably was thought for.
Ant builder: Be more gracious with test naming

- Allow "Benchmark" to appear anywhere in the test name to have it
recognized as a benchmark
Ant builder: Put unit tests into JAR

- I want to add unit tests which run a full Freenet node. This requires
WOT to be loaded as a plugin, so we have to compile a JAR.
- The location to which tests are compiled is changed from
"${build-test}" to "${build-test}/test" so we can stick the JAR into
${build-test} without it being on its own include path. I decide against
putting it into dist/ because the distribution should only contain stuff
which *has* been tested. Also there is no sense in distributing unit
test JARs IMHO.
- The <jar> tag is inspired by the one in the "dist" <target>.
- The <zipfileset> which includes the unit test classes in the test
runner includes "**/*Test*.class" instead of "**/*.class" because
including all files would pass the main WOT classes to JUnit, which
would fail because they are not tests.
So we use the heuristic of havin anything be a test which has "Test" in
the name. I have grepped the directory listing of all test classes, and
they currently all have "Test" in the name, so this will succeed for
the existing classes. If a developer adds a new test, he is very likely
to try to run it and check for its results - so its likely that
people will notice if new tests do not get included because they don't
have "Test" in the name.
- A quick Google search resulted in the claim that <jvmarg> is safe to
include unqouted ${} paths as long as we only use one in one <jvmarg>
tag. I have not tested this with a path which contains spaces, but will
do once a test is implemented which actually uses the JAR.
Merge remote-tracking branch 'origin/master' into use-plugin-fcp-rewrite
Ant builder: Fix accidentally removed "-Djava.awt.headless=true"

- Was accidentally removed in
the previous commit abb74eeb73236d085202e69c76de34e536679d6c. Sorry
Merge remote-tracking branch 'origin/master' into use-plugin-fcp-rewrite