- when setting the sql_mode to strict you now get a warning telling
   that one should also set some other modes since those will be
   part of strict in the future.
 - this causes tests which modifies sql_mode and then set it back
   to default to get an additional warning when setting the sql_mode
   back
 - record the warning in the result file, just like have been
   done elsewhere
 - also 'strict' sql_mode no longer contains NO_ZERO_DATE,
   so in a few test there is a need to explicitly turn off
   also that mode to allow the specific table to be created.
 - see WL8596