* By allowing for a user-pointer to be passed into the constructor,
  thread-safety can be achieved much better.
* Having all the communicators in a read-only struct clarifies
  ownership and simplifies their passing around.

* Use NAG 7.1 in CI setup instead of 7.2 because 7.2 is not yet
  supported in the Docker image.
* Use our libtool patches for autoreconf (required for working NAG builds).

* While the handle remains unchanged and INTENT(IN) suffices
  from the point-of-view of the Fortran compiler,
  having INTENT(INOUT) here makes it much more obvious, that
  the internally referenced object will indeed be changed.

* And rename accordingly.

* xt_mpi_fint_kind is also needed in client code to prevent
  some gfortran warnings.

* This will also catch files where the name is composed of tabs and spaces.

* The previous code claimed to do so, but only handled
  modified files.

This reverts commit 71b90ca6.

* For rsync 3.2.0 the documentation switched the options around when
  changing from yodl to markdown for the internal format.

* This is meant to cause recompilation whenever any yaxt Fortran interface
  source file changes.

* MPI might need more space than the absolute minimum.