MDEV-24818 Concurrent use of InnoDB table is impossible until the first transaction is finished

In MDEV-515, we enabled an optimization where an insert into an
empty table will use table-level locking and undo logging.
This may break applications that expect row-level locking.

The SQL statements created by the mysqldump utility will include the
following:

    SET unique_checks=0, foreign_key_checks=0;

We will use these flags to enable the table-level locked and logged
insert. Unless the parameters are set, INSERT will be executed in
the old way, with row-level undo logging and implicit record locks.

mysql-test/suite/innodb/r/insert_into_empty.result

@@ -1,3 +1,4 @@
+SET foreign_key_checks=0, unique_checks=0;
 #
 # MDEV-24715 Assertion !node->table->skip_alter_undo
 #