WL#12270: USE INNODB TO STORE WARNINGS IN MTR

Affects: Server-8.0   —   Status: Complete   —   Priority: Medium

MTR currently creates the tables test_suppressions and global_suppressions in
MyISAM (code in include/mtr_warnings.sql ) This must be changed to use InnoDB. 
Additionally the error_log table in include/check-warnings.test still MyISAM which 
must be changed too.

This WL is required to aid creation of MTR suite which can run without MyISAM.
FR1) MTR tables test_suppressions, global_suppressions and error_log must now be 
created using InnoDB.

FR2) For tests where check warnings cannot be done, the check for warnings can be 
skipped by passing --nowarnings in the .opt file.
This worklog results in no user-visible changes.
This worklog is to ensure MTR tables test_suppressions, global_suppressions and 
error_log are created using InnoDB and not MyISAM.
For some tests that set innodb_force_recovery > 3, check-warnings can not be 
executed as all tables become Read Only and check-warnings fails to execute. For 
such tests a mechanism to skip check-warnings by passing --nowarnings in the .opt 
file is implemented.