WL#12926: Deprecate log_bin_use_v1_row_events

Affects: Server-8.0   —   Status: Complete

EXECUTIVE SUMMARY
=================

This worklog implements a deprecation warning when user sets or reads
the value of log_bin_use_v1_row_events.

BACKGROUND
==========

- Back in MySQL 5.6, the concept of v1 and v2 row events was
  introduced as needed by NDB.

  The motivation was: "Allow extra data to be appended to a
  Rows_log_event.  This allows per-row information to be communicated
  from Master to Slave."

- 5.5 generates and reads only v1 row events.
- 5.6, 5.7 and 8.0 can parse and interpret v1 and v2 row events
- 5.6, 5.7 and 8.0 have an option to choose which version of events to
  generate. This option is "log_bin_use_v1_events".
  - If set to 1 v1 row events are generated.
  - If set to 0 v2 row events are generated.
- The option is dynamic and should be dynamic, but there are bugs
  associated with it. But we are deprecating this option so we should
  not fix the bugs.

- log_bin_use_v1_row_events is only needed for RBR replication into
  5.5 slaves.

- We don't support cross-version more than one major version.

- v2 events are extensible and have been the default since MySQL 5.6.