Improve mariadb-binlog implementation for --stop-datetime parameter

Currently, mariadb-binlog assumes all events in binlog are in chronological order. When --stop-datetime is specified, if it process an event reach --stop-datetime, it will skip all subsequent events, even those events may have earlier timestamp than --stop-datetime.

This means --stop-datetime needs to be re-implemented as a filter similar to the different domains of --stop-position GTIDs.

Refer to discussion in : https://github.com/MariaDB/server/pull/3670#discussion_r1884499585 for details.