Support MySQL 8.4 and 9.X in orchestrator

MySQL 8.4 and 9.X have been released by upstream Oracle. Currently orchestrator is not aware of these versions so behaviour is likely to be undefined. Additionally changes in 8.4/9.X may mean that orchestrator may not work as older commands were removed.

Initial checks on potential issues may be:

• replication commands all the new form source/replica rather than the older terms master/slave, the older format no longer works

• some column names or command output also change here along the same lines

Other changes which may be of interest are:

• replication should work from any 8.0.X version to any other 8.0.X version (with X being 35+ or around there), so any minor version checks could potentially be removed

• All MySQL 8.4.X is supposed to be 100 compatible as no feature changes are expected. Thus any code that checks for replication settings should potentially allow for replication to work in any direction between 8.4.X servers

• MySQL 9.X (until it becomes stable, LTS) should have the same “you an only replicate to the same or later version” checks, similar to 8.0 behaviour previously

The new GTID format that was released in 8.3 could potentially treat breakage or Orchestrator being unable to recognise the format and thus compare or handle GTIDs correctly. While this new format will not be exposed or used by default, it’s possible to inject this and then orchestrator might break.

There may be other things that are broken. I’m not sure if there’s already an existing MYSQLDIST ticket related to handling MySQL 8.4+ so apologies if this is a duplicate. However, for ongoing use of MySQL 8.4+ with orchestrator it’s most likely that some changes to orchestrator will be needed.