MDEV-7491: Occasional test failure in innodb.group_commit_crash_no_optimize_thread

The test case deliberately crashes the server. If this crash happens in the
middle of a page write, InnoDB crash recovery recovers the page from the
doublewrite buffer, writing a message to the error log that is flagged as a
test failure by mysql-test-run. So add a suppression for this.

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

+call mtr.add_suppression("InnoDB: Warning: database page corruption or a failed");
 CREATE TABLE t1(a CHAR(255),
 b CHAR(255),
 c CHAR(255),

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

+call mtr.add_suppression("InnoDB: Warning: database page corruption or a failed");
 CREATE TABLE t1(a CHAR(255),
 b CHAR(255),
 c CHAR(255),

mysql-test/suite/innodb/t/group_commit_crash.test

@@ -9,6 +9,8 @@
 --source include/have_debug.inc
 --source include/have_log_bin.inc
 
+call mtr.add_suppression("InnoDB: Warning: database page corruption or a failed");
+
 let $file_format_max=`SELECT @@innodb_file_format_max`;
 CREATE TABLE t1(a CHAR(255),
                 b CHAR(255),

mysql-test/suite/innodb/t/group_commit_crash_no_optimize_thread.test

@@ -9,6 +9,8 @@
 --source include/have_debug.inc
 --source include/have_log_bin.inc
 
+call mtr.add_suppression("InnoDB: Warning: database page corruption or a failed");
+
 let $file_format_max=`SELECT @@innodb_file_format_max`;
 CREATE TABLE t1(a CHAR(255),
                 b CHAR(255),