Needed for the following commits.

NO_CHANGELOG=build
NO_DOC=build
NO_TEST=build

Needed for the following commit.

NO_CHANGELOG=build
NO_DOC=build
NO_TEST=build

The patch introduces CTest support, see [1] and [2]: the CMake
target `test` was replaced by builtin CMake target that executes
ctest-based tests. The target `test` that runs `test-run.py` was
renamed to `test-all`. Build and test steps remains the same
as before:

$ cmake -S . -B build
$ cmake --build build --parallel
$ cmake --build build --target test

One could use `ctest` tool instead:

$ ctest --print-labels
Test project <snipped>
All Labels:
  LuaJIT-tests
  PUC-Rio-Lua-5.1-tests
  app
  app-luatest
  app-tap
  box
  box-luatest
  box-py
  <snipped>

$ ctest                          # Run all tests.
$ ctest -L app-luatest           # Run tests by label.
$ ctest --rerun-fail             # Run only the tests
                                 # that failed previously.
$ ctest --verbose                # Print details to stdout.
$ ctest --output-on-failure      # Print details to stdout
                                 # on test failure only.

The possible benefits of using CTest are:

- test execution triggers rebuilding of dependencies automatically
- close integration with a build system options
  (ASAN/UBSAN/Debug/Release etc.) and without setting builddir
  manually
- versatile tool for running different kind of tests (functional,
  performance, fuzzing tests) made using different test frameworks
  and libraries: TAP, luatest, diff-based tests, Google Benchmark,
  LuaJIT-based and PUC Rio Lua-based tests etc.
- no more stderr and stdout suppressing
- easy access to a raw command line for running tests manually
  for debug purposes (see `ctest --verbose`)

Note that CMake targets test-unit, test-unit-force, test-func,
test-func-force, test-all, 1mops_write_perftest,
box_select_perftest, tarantoolgh-7089-vclock-copy_perftest,
uri_escape_unescape_perftest, column_scan_perftest,
tuple_perftest, bps_tree_perftest, light_perftest, small_perftest,
memtx_perftest are still operating for backward compatibility.

Note that it is not possible to add dependencies to `add_test()`
in CMake, see [3]. CMake 3.7 introduces FIXTURES_REQUIRED [4] and
FIXTURES_SETUP [5], but these test properties cannot be used - the
currently supported CMake version is lower. This is workarounded
by the introduced macro `add_test_suite_target` that adds
a CMake-test for each testsuite that executes a target that builds
test dependencies.

1. https://cmake.org/cmake/help/latest/manual/ctest.1.html
2. https://cmake.org/cmake/help/book/mastering-cmake/chapter/Testing%20With%20CMake%20and%20CTest.html
3. https://gitlab.kitware.com/cmake/cmake/-/issues/8774
4. https://cmake.org/cmake/help/latest/prop_test/FIXTURES_REQUIRED.html
5. https://cmake.org/cmake/help/latest/prop_test/FIXTURES_SETUP.html
6. tarantool/luajit@9f1137b

Related to tarantool#5000.

NO_CHANGELOG=testing
NO_DOC=testing

The patch add CTest support for performance tests. Now it is
possible to execute these tests using `ctest` tool with labels
`performance-lua`, `performance-c` and `performance`.

NO_CHANGELOG=build
NO_DOC=build
NO_TEST=build

The patch add CTest support for fuzzing tests. Now it is
possible to execute these tests using `ctest` tool with labels
`fuzzing-c` and `fuzzing`.

NO_CHANGELOG=build
NO_DOC=build
NO_TEST=build

The patch add CTest support for fuzzing tests written in Lua.
Now it is possible to execute these tests using `ctest` tool with
labels `fuzzing-lua` and `fuzzing`.

Follows up commit 33670ea ("test/fuzz: add an engine fuzzing test").

NO_CHANGELOG=build
NO_DOC=build
NO_TEST=build

The patch add support of luatest's tests by CTest.

The environment variable `VARDIR`, used by luatest [1], is set to
`/tmp/t`, the same value used by test-run.py.

The CMake target `tarantool` is not used a pseudotest "*-deps",
because target `box_generate_lua_sources`, required for building
tarantool and that builds Lua source files, being run in parallel
can corrupt generated files.

The tests in luatest suites can be executed by `ctest`
using labels app-luatest, box-luatest, engine-luatest,
metrics-luatest, replication-luatest, sql-luatest, vinyl-luatest.

1. test-run/lib/luatest/luatest/server.lua.

NO_CHANGELOG=build
NO_DOC=build
NO_TEST=build

The patch introduce a target `test-force-ctest` that runs
functional regression tests and this target is used in
GHA workflow `static_build_cmake_linux`.

NO_CHANGELOG=build
NO_DOC=build
NO_TEST=build