Do not use just-built CMake to install itself when cross-compiling (#15248)

The special case added by commit v2.4.0~3051 (When building CMake
itself, use the new cmake to install so that the current cmake can be
overwritten, 2004-06-09) does not make sense when cross-compiling.
Tests: Build config-dependent tests in the same config they run

The CPackComponentsForAll-*, GeneratorExpression, and
TestsWorkingDirectory tests all build binaries that they later
need to run or package for the tested configuration.  Tell the
'ctest --build-and-test' call to use the same configuration
for driving the build process.
Help: Revise and format 'add_custom_target' docs

Format the reStructuredText markup manually.  Organize the command
options into a definition list.  Use inline markup to cross-reference
related documents.
VS: Change Nsight Tegra 2.0 Project Revision Number from 8 to 9

A hotfix to Nsight Tegra 2.0 needed to increase the project number.
Teach CMake to generate the newer number for this version.
Help: Document add_custom_command marking outputs GENERATED
Merge topic 'fix-config-dependent-tests'

0854d45b Tests: Build config-dependent tests in the same config they run
Merge topic 'no-cmake-self-install-when-cross-compiling'

15f55cca Do not use just-built CMake to install itself when cross-compiling (#15248)
Merge topic 'doc-add_custom_target'

66ea634b Help: Revise and format 'add_custom_target' docs
Merge topic 'vs-nsight-tegra-version'

bb3c87f1 VS: Change Nsight Tegra 2.0 Project Revision Number from 8 to 9
Merge topic 'doc-add_custom_command'

0cacf739 Help: Document add_custom_command marking outputs GENERATED