ALTER TABLE and replication should convert old row_end timestamps to new timestamp range

MDEV-32188 make TIMESTAMP use whole 32-bit unsigned range

- Added --update-history option to mariadb-dump to change 2038
  row_end timestamp to 2106.
- Updated ALTER TABLE ... to convert old row_end timestamps to
  2106 timestamp for tables created before MariaDB 11.4.0.
- Fixed bug in CHECK TABLE where we wrongly suggested to USE REPAIR
  TABLE when ALTER TABLE...FORCE is needed.
- mariadb-check printed table names that where used with REPAIR TABLE but
  did not print table names used with ALTER TABLE or with name repair.
  Fixed by always printing a table that is fixed if --silent is not
  used.
- Added TABLE::vers_fix_old_timestamp() that will change max-timestamp
  for versioned tables when replication from a pre-11.4.0 server.

A few test cases changed. This is caused by:
- CHECK TABLE now prints 'Please do ALTER TABLE... instead of
  'Please do REPAIR TABLE' when there is a problem with the information
  in the .frm file (for example a very old frm file).
- mariadb-check now prints repaired table names.
- mariadb-check also now prints nicer error message in case ALTER TABLE
  is needed to repair a table.

mysql-test/main/mysql_upgrade_mysql_json_with_plugin_loaded.result

@@ -170,12 +170,12 @@ performance_schema
 sys
 sys.sys_config                                     OK
 test
-test.mysql_json_test                               Needs upgrade
-test.mysql_json_test_big                           Needs upgrade
+test.mysql_json_test                               Needs upgrade with ALTER TABLE FORCE
+test.mysql_json_test_big                           Needs upgrade with ALTER TABLE FORCE
 
 Repairing tables
-test.mysql_json_test                               OK
-test.mysql_json_test_big                           OK
+`test`.`mysql_json_test`                           OK
+`test`.`mysql_json_test_big`                       OK
 Phase 7/8: uninstalling plugins
 Phase 8/8: Running 'FLUSH PRIVILEGES'
 OK