Update to upstream version '10.1.40'
with Debian dir 15cc3e72f57cb6e256589bbd093000a8153d41c0

Update to upstream version '10.1.39'
with Debian dir b02cce09df65b5e8c30006c7cfbae4ad19f48522

Also skip unstable rpl tests, as is also done in mariadb-10.3 packaging.

By default the policy-rc.d exits with code 101 and prevents from services
inside Docker to start with the rationale that it is not needed as the
services will not run by default when a Docker container is started
anyway, but we want the mysql/mariadb service to run so that we can
simulate real install/upgrade scenarios.

This makes e.g. Gitlab-CI run 3x as fast as without.

Also cherry-pick autopkg tests fixes from
mariadb-10.3@1ba2a673

Upstream developer confirmed the test is unimportant and it is OK
to allow it to fail.

https://jira.mariadb.org/browse/MDEV-17865

Also migrate to using dockerbuilder following upstream Salsa-CI changes.

See https://salsa.debian.org/salsa-ci-team/dummypackage/tree/master/debian

Update to upstream version '10.1.38'
with Debian dir bf5887327d488168695833ed7a82628c14b6eac8

The interpreter used is installed at another location on Debian systems.
In general, env should not be used in shebangs but the real name instead.

Modeled after what Debian Salsa CI team uses, see
https://salsa.debian.org/salsa-ci-team/pipeline/raw/master/salsa-ci.yml

Modified a bit to stay under the 4 MB log size limit
and 100 MB artefact limit.

Attempted to get all of Salsa CI working, but ran into failures and was
unable to overcome all of them, so leaving some parts of the pipeline
disabled for now.

The rename of tokuft_logdump is necessary for the package to build
so it is justified even in a stable release. Also adding a few new
man pages is completely safe.

Upstream version 10.1.37