software/erp5: fix flappy test_logrotate_and_slow_query_digest test

This test uses the default config of having mariadb log queries taking more
than 1 second, then makes two slow queries and check that these two queries
are logged and included in pt-query-digest report.

Sometimes this test fail because there are more slow queries than the two
expected, in the snapshots, we can see that reports also contain:

    SHOW TABLE STATUS FROM `mysql` LIKE 'time_zone_transition'\G
    SHOW CREATE TABLE `mysql`.`time_zone_transition`\G

but these queries are not made by the test. They are probably made by
mysql_upgrade script. Such queries can take more than 1 second sometimes
and when they do the test fail because there are more slow queries than the
expected.

To prevent this kind of intermitent failures, make our test queries slower
and configure mariadb to log queries after a longer delay (3 seconds).
Hopefully these unrelated queries should not take more than 3 seconds.
8 jobs for failover-backend
Status Job ID Name Coverage
  External
passed SlapOS.SlapRunner.ResilienceTest-Master

00:24:30

failed SlapOS.SlapRunner.ResilienceTest-Master.ERP5

00:25:11

failed SlapOS.SoftwareReleases.IntegrationTest-Master.Python2

13:37:35

passed SlapOS.SoftwareReleases.IntegrationTest-Master.Python3

06:08:32

passed SlapOS.SlapRunner.ResilienceTest-Master

00:24:31

failed SlapOS.SlapRunner.ResilienceTest-Master.ERP5

00:26:58

failed SlapOS.SlapRunner.ResilienceTest-Master.ERP5

00:27:12

failed SlapOS.SoftwareReleases.IntegrationTest-Master.Python2