GTID looses all binlog state after crash if InnoDB is disabled

If InnoDB is disabled (and no other XA-capable engine is enabled), then the
server does not do any binlog crash recovery during restart after a crash.

This is not sufficient for GTID, as we need to recover the last GTID logged
into the binlog (so that we can know the next seq_no to assign to new GTIDs
and how to reply to connecting slaves etc.).

Thus, even in non-XA case we still need to scan the binlog and do crash
recovery, though the XA part of it can be ignored.

Same when using using_heuristic_recover().

(MyISAM of course is not crash safe, but it is still better to loose a few
seconds of state or whatever compared to all state since prior server start).