ci: generate single code coverage report for C++ code

See merge request asapo/asapo!242

As mentioned on
https://gcc.gnu.org/onlinedocs/gcc-4.9.4/gcc/Debugging-Options.html#Debugging-Options,
the option `--coverage` "is a synonym for -fprofile-arcs -ftest-coverage
(when compiling) and -lgcov (when linking)".

This commit replaces all the `coverage*` CTest C++ tests with a single
CMake target that generates a single report for all the C++ tests
instead of one report for each `coverage*` CTest C++ test.

In addition, the CMake target uses
[fastcov](https://github.com/RPGillespie6/fastcov) instead of
[lcov](https://github.com/linux-test-project/lcov) because `fastcov` is
at least an order of magnitude faster than `lcov` at the moment.

Note that `fastcov` and `lcov-to-cobertura-xml` were downloaded using
the following commands:

```sh
$ bash 3d_party/fastcov/download.sh
Installing from commit https://github.com/RPGillespie6/fastcov/commit/40dffe81d62c0d897afe4108f3b5489487ff3bce into 3d_party/fastcov
  - https://raw.githubusercontent.com/RPGillespie6/fastcov/40dffe81d62c0d897afe4108f3b5489487ff3bce/fastcov.py  --> fastcov.py
  - https://raw.githubusercontent.com/RPGillespie6/fastcov/40dffe81d62c0d897afe4108f3b5489487ff3bce/LICENSE     --> LICENSE
  - https://raw.githubusercontent.com/RPGillespie6/fastcov/40dffe81d62c0d897afe4108f3b5489487ff3bce/README.md   --> README.md

$ bash 3d_party/lcov-to-cobertura-xml/download.sh
Installing from commit https://github.com/eriwen/lcov-to-cobertura-xml/commit/18489f195e5389fca3fec53608a5503af759ee44 into 3d_party/lcov-to-cobertura-xml
  - https://raw.githubusercontent.com/eriwen/lcov-to-cobertura-xml/18489f195e5389fca3fec53608a5503af759ee44/LICENSE     --> LICENSE
  - https://raw.githubusercontent.com/eriwen/lcov-to-cobertura-xml/18489f195e5389fca3fec53608a5503af759ee44/README.md   --> README.md
  - https://raw.githubusercontent.com/eriwen/lcov-to-cobertura-xml/18489f195e5389fca3fec53608a5503af759ee44/lcov_cobertura/lcov_cobertura.py    --> lcov_cobertura/lcov_cobertura.py
```

ci: extract CI job template to build docker images

See merge request asapo/asapo!243

The following CI jobs are now using the CI job template
`.docker-create-build-env` and were moved into `.gitlab-ci.yml`:

- deploy/build_env/centos/gitlab-ci-build-docker.yml
  - docker-create-asapo-packages-centos7-build-env
  - docker-create-asapo-packages-centos8-build-env

- deploy/build_env/debians/gitlab-ci-build-docker.yml
  - docker-create-asapo-packages-debian9-build-env
  - docker-create-asapo-packages-debian10-build-env
  - docker-create-asapo-packages-debian11-build-env
  - docker-create-asapo-packages-debian12-build-env

- gitlab-ci-build-docker.yml
  - docker-create-asapo-packages-manylinux-build-env

- deploy/build_env/services-linux/gitlab-ci-build-docker.yml
  - docker-create-asapo-services-linux-build-env

- deploy/build_env/services-windows/gitlab-ci-build-docker.yml
  - docker-create-asapo-services-windows-build-env

- deploy/build_env/site/gitlab-ci-build-docker.yml
  - docker-create-asapo-site-build-env

- deploy/build_env/ubuntu/gitlab-ci-build-docker.yml
  - docker-create-asapo-packages-ubuntu1804-build-env
  - docker-create-asapo-packages-ubuntu2004-build-env

- deploy/secondary_services/fluentd_elastic/gitlab-ci-build-docker.yml
  - docker-create-asapo-secondary-fluentd-elasticsearch

**Note**: in the process, the rules of the CI jobs
`docker-create-asapo-packages-ubuntu1804-build-env` and
`docker-create-asapo-packages-ubuntu2004-build-env` have been modified.
These rules were probably incorrect because they were triggering a build
of the Docker container when pushing the first version of a branch.

Style: remove trailing whitespaces

See merge request asapo/asapo!246

...  when running `git blame`

- Add the pre-commit hook `trailing-whitespace` to `.pre-commit-config.yaml`
- Apply the hook to all files with the command `pre-commit run -a`

Add all streams in one collection

See merge request asapo/asapo!245

docs: use architectural decision records to justify design decisions

See merge request !247

See https://adr.github.io/.

I used [`adr-tools`](https://github.com/npryce/adr-tools) to create the
initial Architecture Decision Record (ADR):

```sh
adr init docs/contributing/architecture/decisions
```

build: enable building from a directory which is not a subdirectory of the source directory

See merge request !248

Rationale: building `ASAP::O` from a Docker image on macOS inside a
subdirectory of the source directory can be slow because the files
inside the subdirectory are visible from macOS and macOS does not seem
to handle well when many files changed within a virtual machine. It is
therefore faster to compile from a directory that is not mounted on the
Docker image, which cannot be a subdirectory of the source directory.

Move DB requests to broker

See merge request !240

Comment-out seconds attempt to ingest dataset in the first attempt failed because if the duplicate error.

build: use same Python interpreter in all CMake scripts

See merge request asapo/asapo!230

These modules were introduced in CMake 3.12 as mentioned on
https://cmake.org/cmake/help/git-stage/release/3.12.html#modules. So
these modules are not needed in `ASAP::O` code base except when building
on Ubuntu 18.04 that contains CMake 3.10. As a workaround, the CI job
`build-packages-ubuntu1804` defines the environment variable
`Python_EXECUTABLE` so that CMake does not need the `FindPython.cmake`
module to find the Python interpreter.

Providing the value of `Python_EXECUTABLE` using an environmnet variable
instead of a CMake argument can simplify calls to CMake:

```sh
cmake .. -DENABLE_LIBFABRIC=ON -DCMAKE_BUILD_TYPE="Release" \
  -DBUILD_CLIENTS_ONLY=ON -DBUILD_PYTHON_PACKAGES=source \
  -DNUMPY_VERSION=$NUMPY_VERSION -DPython_EXECUTABLE=python3

export Python_EXECUTABLE=python3
cmake .. -DENABLE_LIBFABRIC=ON -DCMAKE_BUILD_TYPE="Release" \
  -DBUILD_CLIENTS_ONLY=ON -DBUILD_PYTHON_PACKAGES=source \
  -DNUMPY_VERSION=$NUMPY_VERSION
```

This avoids using different Python interpreters for different tasks and
therefore avoid surprises.

Note: CMake files for Windows were not fixed because no Windows
CI runner checks that `ASAP::O` compiles on Windows.

test: reduce waiting time when locally starting `ASAP::O` services

See merge request asapo/asapo!239

build: disable optimizations when building `go` code in Debug mode

See merge request asapo/asapo!238

doc: remove `data_nbytes` from Python Producer client documentation

See merge request asapo/asapo!235

This commit makes `run_asapo.sh` monitor the status of the services
started using `supervisord` so that it exits when all services are
running instead of waiting for 20 seconds.

Debugging Go code built without optimizations is easier, as mentioned on
https://go.dev/doc/gdb#Introduction:

> When you compile and link your Go programs with the gc toolchain on
> Linux, macOS, FreeBSD or NetBSD, the resulting binaries contain DWARFv4
> debugging information that recent versions (≥7.5) of the GDB debugger
> can use to inspect a live process or a core dump.
>
> Pass the '-w' flag to the linker to omit the debug information (for
> example, go build -ldflags=-w prog.go).
>
> The code generated by the gc compiler includes inlining of function
> invocations and registerization of variables. These optimizations can
> sometimes make debugging with gdb harder. If you find that you need to
> disable these optimizations, build your program using go build
> -gcflags=all="-N -l".
>
> If you want to use gdb to inspect a core dump, you can trigger a dump
> on a program crash, on systems that permit it, by setting
> GOTRACEBACK=crash in the environment (see the runtime package
> documentation for more info).

... by making `data_nbytes` a C function instead of a Python function.
See
https://notes-on-cython.readthedocs.io/en/latest/function_declarations.html
for the difference between `def` and `cdef` in Cython code.

ci: run tests of Python client in CI before deploying containers and packages

See merge request asapo/asapo!237

build: add `raw-loader` dependency for building `docs/site`

See merge request asapo/asapo!236