Allow using Java in a cross-compilation toolchain

Since Java is a portable language, if you want to use Java when
cross-compiling, UseJava uses the JVM installed on the host.  So in this
case, we must use set CMAKE_JAVA_INCLUDE_FLAG_SEP for the current host.
CMake Nightly Date Stamp
fix regex to match memcheck timing
fix another matching problem because of mixed stdout/stderr
make another attempt to set the test configuration type

Other tests do the same, although I don't understand what's going on here.
Let's see if it works ;)
Merge topic 'MemChecker-improvements' into next

4ee4934 make another attempt to set the test configuration type
5d8a6d1 fix another matching problem because of mixed stdout/stderr
18ae1cc fix regex to match memcheck timing
CTest: fix comment documenting cmBoundsCheckerParser class

This was obviously copied from Source/cmGlobalXCodeGenerator.cxx during
implementation but the comment was forgotten.
Tests: add a test with custom options passed to valgrind
Merge topic 'MemChecker-improvements' into next

cc5816b Tests: add a test with custom options passed to valgrind
0dd0c3c CTest: fix comment documenting cmBoundsCheckerParser class
Merge topic 'UseJava-cross-compile' into next

778aacc Allow using Java in a cross-compilation toolchain
another try to get the configuration in MemChecker tests right

Suggested by Brad King.
Merge topic 'MemChecker-improvements' into next

b353a2d another try to get the configuration in MemChecker tests right
Revert "tests: try to fix test failures due to stale files"

This reverts commit 5a768f7f169e49b76c33fa5210297ce5f79aed70.

The dashboard machines are cleaned up, no need to keep this around.
Merge topic 'MemChecker-improvements' into next

85cd4c2 Revert "tests: try to fix test failures due to stale files"
fix another timing regex
Merge topic 'MemChecker-improvements' into next

00f1e50 fix another timing regex
Tests: create output files for all memory checkers

The dummy memory tester implementation now understands the command line
switches for all memory checkers to redirect the output to a file. This avoids
triggering the error cases for BoundsChecker and Purify because the output file
does not exist.
CTest: use an output file for Valgrind (#14110)

This makes sure Valgrind output will not screw up tests that match on the
output.
CTest: remove unreachable code and CTestTestMemcheckUnknown test

The memory checker command can't be quoted at this point, because previously it
has been tested that the given file exists, which will fail if the name is
quoted. The CTestTestMemcheckUnknown test aimed to test this case, has always
failed to do so and serves no useful purpose therefore.
Tests: remove code duplication in CTestTestMemCheck tests

The code for the tests is basically the same for all those subtests, so have
one template and configure that for as many tests as possible to make it
easier maintainable.