MDEV-9077 - port sys schema to MariaDB

- Innodb is not always available, which means t is not always
possible to use innodb system variables, or innodb information schema
tables.

Thus creation of objects that use Innodb information_schema is enclosed
into BEGIN NOT ATOMIC blocks with dummy SQLEXCEPTION handler.

- sys_config table uses Aria, just like other system tables.

- several tables that exist in MySQL, do not exist in MariaDB
   performance_schema.replication_applier_status, mysql.slave_master_info,
   mysql.slave_relay_log_info

scripts/sys_schema/tables/sys_config.sql

@@ -24,4 +24,6 @@ CREATE TABLE IF NOT EXISTS sys_config (
     value VARCHAR(128),
     set_time TIMESTAMP DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP,
     set_by VARCHAR(128)
-) ENGINE = InnoDB;
+) ENGINE = Aria transactional=1;
+
+

scripts/sys_schema/tables/sys_config_data_57.sql

@@ -22,3 +22,5 @@ INSERT IGNORE INTO sys.sys_config (variable, value) VALUES
     ('diagnostics.allow_i_s_tables', 'OFF'),
     ('diagnostics.include_raw', 'OFF'),
     ('ps_thread_trx_info.max_length', 65535);
+
+FLUSH TABLES sys.sys_config;