There have been push force on master branch, and 1.0.309 seems to be the
result of merging an old version of master branch, the commits between
1.0.308 and 1.0.309 are same as commit on master branch but with
different hashes and when we try to merge master in 1.0 there are
conflicts.

This commit resets to the same state as 1.0.308, it was done with:

  git resore --source 1.0.308 :/
  git commit -a

so it revert all these commits so that we can merge master again.

- MariaDB 10.3.38 & 10.4.28
- mroonga 13.00
- groonga 13.0.0
- groonga-normalizer-mysql 1.2.1

We stopped using it because of 2 data integrity issues:
- https://jira.percona.com/browse/PS-5569 ("FT index corrupt")
- https://jira.percona.com/browse/PS-4291 ("DELETE sometimes do nothing")

TokuDB is also already disabled because transparent huge pages are
enabled by default.

There are more log files with neo

To run the benchmark locally:

 - Install software/slapos-sr-testing and create an instance
 - Source the shell script published by the instance to setup
   environment variables
 - execute `python_for_test -m unittest -v  test.benchmarks`

This promise was generally used to check the connection quality to the
backend with ICMP, by using ping. This is currently obsoleted by health-check
and other parameters in that group.

The parameter to setup the promise is provided by shared instance requester,
that person has no access to those results, as shared instances can't be
monitored directly, all results are only available to the cluster operator in
contrast to health-check, which results are logged to backend_log, to which
shared instance requester has access.

See merge request nexedi/slapos!1348

See merge request !1345