Don't use CREATE TABLE AS SELECT ... with mySQL

[SamWheating]

Closes: #19988

Splitting this CREATE TABLE AS SELECT query into two queries (CREATE TABLE LIKE .. followed by INSERT INTO) because the former doesn't play nicely with MySQL.

This PR is inherently difficult to test/validate, but I ran the proposed queries against the metadata database in our development environment (where we first ran into this issue) and was able to replicate the issue and verify the fix:

// replicating the issue:

MySQL [airflow] > create table _airflow_moved__2_2__task_instance as select source.* from task_instance as source;
ERROR 1786 (HY000): Statement violates GTID consistency: CREATE TABLE ... SELECT.

// Validating that splitting the query fixes the issue

MySQL [airflow] > create table _airflow_moved__2_2__task_instance like task_instance;
Query OK, 0 rows affected (0.063 sec)

MySQL [airflow] > INSERT INTO _airflow_moved__2_2__task_instance select source.* from task_instance as source left join dag_run as dr on (source.dag_id = dr.dag_id and source.execution_date = dr.execution_date) where dr.id is null;
Query OK, 22900 rows affected (2.110 sec)

Tomorrow I can create a patched image with these changes and validate the fix in our development environment.

---

^ Add meaningful description above

Read the Pull Request Guidelines for more information.
In case of fundamental code change, Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in UPDATING.md.

[github-actions]

The PR most likely needs to run full matrix of tests because it modifies parts of the core of Airflow. However, committers might decide to merge it quickly and take the risk. If they don't merge it quickly - please rebase it to the latest main at your convenience, or amend the last commit of the PR, and push it with --force-with-lease.

[ashb]

Can you define "doesn't play nicely with"? Cos in my testing it did work (but I didn't test mysql beyond one or two rows.

Duh, read the full error message Ash.

[ashb]

Ah, This doesn't play nicely when replication is turned on.

[ashb]

I am amazed at MySQLs ability to find new ways to make me sad.

[potiuk]

I am amazed at MySQLs ability to find new ways to make me sad.

Very, very, very much so. I expressed my feelings on MySQL today at the talk I gave at Data Science Summit a bit after I found out that about half of the audience used it, unfortunately. I hope that brings more people to Postgres.