[FebArch]

Implements SHOW BINLOG EVENTS FROM 'gtid' [TO 'gtid'] for the binlog in engine (MDEV-40289).

What works:

• A GTID position starts after the point just after the FROM <gtid>, as Kristian Nielsen explained in this #New Members > MDEV-40289 Improve SHOW BINLOG EVENTS.
• TO stops after the given GTID.
• A bad GTID text gives ER_INCORRECT_GTID_STATE.
• New test binlog_in_engine.binlog_events_gtid, including a range that crosses binlog files.

Open questions:

• Is main the right branch for this feature, or should it go elsewhere?
• What should FROM 100 TO 'gtid' do (a byte position mixed with a GTID)?
• Should FROM '' be an error? Today it shows all events.
• A GTID that is not found gives an empty result today. Should it be an error?
• Multi-domain positions like '0-1-9,1-1-1' are not covered yet. I am not sure one skip flag for all domains is correct.
• Next: a test with different @@gtid_domain_id values, and a copy of the test under binlog_storage_engine=innodb, as Brandon suggested.

[ParadoxV5]

(I replied to (current) open questions on Zulip, #New Members > MDEV-40289 Improve SHOW BINLOG EVENTS @ 💬.)