Add missing MySQL 8.0+ binlog event types (36-42)

[cyppe]

Problem

The ConstEventType enum is missing all event types added in MySQL 8.0+ (types 36–42), causing a ValueError crash when the library encounters any of them:

[ValueError]
39 is not a valid backing value for enum MySQLReplication\Definitions\Const\EventType

The most commonly triggered one is PARTIAL_UPDATE_ROWS_EVENT (type 39), which MySQL emits when binlog_row_value_options=PARTIAL_JSON is enabled — a common optimization for tables with JSON columns.

Another likely trigger is TRANSACTION_PAYLOAD_EVENT (type 40), emitted when binlog_transaction_compression is enabled.

The crash occurs in EventInfo::__construct() where ConstEventType::from() is called with an unrecognized type value.

Current workaround (lossy)

Users can disable the MySQL settings that emit these events (binlog_row_value_options= and binlog_transaction_compression=OFF), but this means MySQL falls back to writing full row images — losing the binlog space savings these features provide. More importantly, without this fix there is no way to use these MySQL features with this library at all.

Changes

1. Added all missing MySQL 8.0+ event types to ConstEventType, per binlog_event.h:

   Type	Name	Trigger
   36	TRANSACTION_CONTEXT_EVENT	Group Replication
   37	VIEW_CHANGE_EVENT	Group Replication
   38	XA_PREPARE_LOG_EVENT	XA transactions
   39	PARTIAL_UPDATE_ROWS_EVENT	binlog_row_value_options=PARTIAL_JSON
   40	TRANSACTION_PAYLOAD_EVENT	binlog_transaction_compression=ON
   41	HEARTBEAT_LOG_EVENT_V2	MySQL 8.0.26+ heartbeat
   42	GTID_TAGGED_LOG_EVENT	Tagged GTIDs

2. Changed from() to tryFrom() in EventInfo — so any future unrecognized event types are handled gracefully instead of crashing. The event will be silently skipped by Event::makeEvent() which already returns null for unhandled types.

Note: This PR adds the event types to the enum so they don't crash, but does not add handlers for them (e.g. decompressing TRANSACTION_PAYLOAD_EVENT or parsing partial JSON diffs from PARTIAL_UPDATE_ROWS_EVENT). These events are silently skipped by Event::makeEvent(). Full handler support could be added in follow-up PRs.

Why CI doesn't catch this

The test workflow's my-cnf only sets binlog_format=row and binlog_rows_query_log_events=ON. It does not enable binlog_row_value_options=PARTIAL_JSON or binlog_transaction_compression=ON, so MySQL never emits event types 39/40 during CI. These are common production settings.

[krowinski]

tx