Binlogging of MEMORY table recreation from server restart is silently deferred

The data in MEMORY tables is temporary and is lost when the server restarts.
To represent this recreation with no data, the server logs a TRUNCATE statement to the binary log.
However, there is no warning about MEMORY tables losing data after a reboot, let alone this TRUNCATE log entry.

Worse, this TRUNCATE entry is not immediately written during startup, but rather when the MEMORY table is accessed.
This means that any desynchronization error (due to data loss) does not occur during the restart phase in maintenance, but instead unexpectedly during operation.
Namely, MDEV-29796 reported that --gtid-strict-mode checks would fail (if the server does not have a different Domain ID from its replication upstreams).