monit: Update to 5.29.0

monit: Update to 5.29.0

For details see:
https://mmonit.com/monit/changes/

    New: Issue #715: The PostgreSQL protocol test has been improved and
    now supports authentication with username, password and database
    when testing connection. Example:

    if failed port 5432
        protocol pgsql username "username" password "12345" database "test"
    then alert

    Previous Monit versions used hardcoded credentials when testing
    connection to postgresql (user=root and database=root). This could
    trigger thousands of messages like this in the postgresql log:

    root@root FATAL:  password authentication failed for user "root"
    root@root DETAIL:  Role "root" does not exist.

    Note: Monit will continue to use the hardcoded credentials (for
    backward compatibility) unless username and password are set.
    New: Issue #973: You can now test program output using a regular
    expression. Syntax:

    IF CONTENT [!]= <regex> THEN action

    Example:

    check program disk0_smart with path "/usr/sbin/nvme smart-log /dev/nvme0"
        if content != "critical_warning[ ]+: 0" then alert

    New: Issue #974: Monit CLI: Added support for the -g (group) option
    to the report command. Example:

    monit -g database report

    Fixed: Issue #991 (Monit 5.28.1 regression): MacOS: Monit didn't
    compile on MacOS 10.13 or older. Thanks to Lutz Mader.

    Fixed: Issue #994 (Monit 5.28.1 regression): The check program
    statement with every did not work properly.

    Fixed: Issue #995: Monit start delay was vulnerable to time jumps
    when Monit is waiting for the delay to pass. Thanks to Daniel Crowe.

    Fixed: Issue #975: Monit CLI: Monit did not report a warning if -s,
    -p, -l, -g or -c command-line options were specified multiple times
    and silently used the last value only. Monit will generate a warning
    now.

    Fixed: Issue #972: Monit GUI: The log view had no size limit when
    reading the Monit log file and could block the browser if the log
    file was large.

    Fixed: Issue #955: If more than one every statement is used in
    a check-service context only the last value is (silently) used.
    We now report a warning in this case.

Signed-off-by: Matthias Fischer <matthias.fischer@ipfire.org>
Signed-off-by: Arne Fitzenreiter <arne_f@ipfire.org>