All other log messages in the script do this already.

This will be useful for running nightly testing against our own
nightly binaries.

Return to scripts including `cmake_common` in an environment suitable
for running additional steps in the original CMake build.

Reported-by: Alan W. Irwin <irwin@beluga.phys.uvic.ca>

At a VS 2017 command prompt the PATH contains a directory that happens
to have a `Git/cmd/git.exe` inside it. However, this executable is not
meant for general use. Revise our use of Git/ path suffixes to be more
specific to its original purpose of searching in the typical
`c:/Program Files*/Git/` installation directories.  Avoid using the
suffixes on PATH entries.

CMake is moving away from a manually-maintained `next` branch to a model
where we maintain a "stage" for each target branch (e.g. `master`) that
consists of the target branch plus some set of MRs merged on top of it.
The job of this testing script is now to test one of the integration
branches or one of their stage branches.  Add infrastructure to create
or convert the local test repository such that it has tracking branches
for each stage branch.  Select one to check out and follow for testing.

KWSys development is moving to a Fork & Merge Request model where we
maintain a "stage" for each target branch (e.g. master) that consists of
the target branch plus some set of MRs merged on top of it.  The job of
this testing script is now to test one of the integration branches or
one of their stage branches.  Add infrastructure to create or convert
the local test repository such that it has tracking branches for each
stage branch.  Select one to check out and follow for testing.

KWSys development is moving to a Fork & Merge Request model
where per-topic testing will be managed by a `refs/test-topics/`
namespace on the upstream repository.  Convert our topic testing
infrastructure to fetch this set of refs and test each one.

Make the build directory after using ctest_empty_binary_directory
because the command reports an error if asked to delete a directory
that exists but does not contain `CMakeCache.txt`.

Reported-by: Raffi Enficiaud <raffi.enficiaud@tuebingen.mpg.de>

The ctest_memcheck step should run the same tests as the ctest_test
step.

Add a "dashboard_hook_started" hook after the ctest_start call.
This gives scripts a chance to override the submission information
that ctest_start loaded from the project's CTestConfig.cmake file.

In commit 523fec52 (Do not assume we are in CTEST_SCRIPT_DIRECTORY,
2012-11-01) we accidentally changed only one of the two references to
CTEST_SCRIPT_DIRECTORY over to cmake_common_dir.

We know that kwsys_common.cmake is next to cmake_common.cmake, but do
not assume both are in CTEST_SCRIPT_DIRECTORY.  Instead compute the
location of kwsys_common from the location of cmake_common.

Drive KWSys dashboard builds everywhere cmake_common is used to drive
CMake dashboard builds.

Since KWSys is an important dependency of CMake we want to test changes
to it everywhere CMake is tested.  Create a dashboard helper script that
runs a normal KWSys dashboard out of its repository and then runs more
KWSys dashboards to test experimental changes in Gerrit.

Remove remnants of dual CVS/Git support.  Remove information duplicated
from CTestConfig.cmake that was needed to work around CTest delayed
initialization problems fixed as of 2.8.2.

Some dashboard builds run on scratch disks that arbitrarily remove files
that have not been accessed in a while.  Since Git uses O_NOATIME for
repository objects the .git repository files may disappear thus
corrupting the repository.  When this happens even "git reset --hard"
will fail, so wipe out the source tree to get a fresh clone.

Use the same OSI-approved 3-clause BSD license that covers CMake.

We no longer support cvs client checkouts from the Git repository.
Dashboard clients may use only Git.