stack/wendelin: Fix mariadb binlog automatic purge
Since mariadb 11.4, binlogs are never purged unless a minumum amount of replicas are connected, 1 by default. This caused binlogs to accumulate forever and take up disk space in mariadb instances without a replica - including mariadb instances that are themselves replicas. Thus all ERP5 deployments with or without replication were affected, and SRs based on stack/lamp such as matomo and nextcloud.
See https://jira.mariadb.org/browse/MDEV-34504
See lists.mariadb.org/thread/EXIBNZ6PY4FQNBIUWJXS7SHKBMJWFPQ for a clear description.
Edited by Xavier Thompson