backport: vtbackup: disable redo log before starting replication (#11330)

[tanjinx]

• vtbackup: disable redo log before starting replication

According to MySQL docs:

As of MySQL 8.0.21, you can disable redo logging using the ALTER
INSTANCE DISABLE INNODB REDO_LOG statement. This functionality is
intended for loading data into a new MySQL instance. Disabling redo
logging speeds up data loading by avoiding redo log writes and
doublewrite buffering.

See: https://dev.mysql.com/doc/refman/8.0/en/innodb-redo-log.html#innodb-disable-redo-logging

We can take advantage of this in vtbackup. This change disables the redo log on MySQL >= 8.0.21 before starting replication, and re-enables the redo log after stopping replication.

• non-fatal error, robus status check, copyright current year

• try checking redo log status in vtbackup e2e test

• retain vtbackup temporary files so we can verify them in e2e test

• make e2e test work with upgrade/downgrade tests

• check for mysql 8.0.21 in e2e test redo log assertions

• fmt.Println debug

• perconnnaaaaaa

• fix e2e flags

• simplify e2e test, revert flags and cnf cruft

• capitalize log msgs

• dont verify redo log for --initial_backup

• address pr comments: fix typo and remove package alias

• address pr comments: report redo log enabled when we can't disable

• rely on mysql server variable to determine if can disable/enable redo log

• split up binary vs. process redo log capability

• simplify further

• Address my own pedantic nits

• Sorry, can't help myself

Description

Related Issue(s)

Checklist

• "Backport to:" labels have been added if this change should be back-ported
• Tests were added or are not required
• Did the new or modified tests pass consistently locally and on the CI
• Documentation was added or is not required

Deployment Notes

[salesforce-cla]

Thanks for the contribution! Before we can merge this, we need @maxenglander to sign the Salesforce Inc. Contributor License Agreement.