upgrade warnings for Maria 10.2 to later versions...effect upon CMSB?

Dave and Team,

Updating the host regarding from MariaDB 10.2 to later versions and the automated upgrade tester raised some flags. 

Upgrade Warnings

The upgrade script has checked your system to see if an upgrade is possible at this time. The system encountered warnings specific to your configuration.

Please click the checkbox next to each warning to indicate that you understand the potential consequences of this upgrade.

  Severity Message

Critical In MariaDB® 10.3, the mysqldump client includes logic for the mysql.transaction_registry table. You cannot use the mysqldump client from an earlier MariaDB release on MariaDB 10.3 and later. For more information about how to upgrade to MariaDB 10.3, read the MariaDB upgrade documentation .

Critical In MariaDB 10.4 and later, the mysql.global_priv table has replaced the mysql.user table. The mysql.user table is converted into a view of the mysql.global_priv table during the database upgrade. The dedicated mariadb.sys user is created as the definer of the new mysql.user view.

Critical The "mytop" package is not compatible due to MDEV-22552. If "mytop" is installed, the upgrade process will uninstall the "mytop" package.

Normal All binaries previously beginning with `mysql` now begin with `mariadb`. Symlinks are created for the corresponding mysql commands to ensure backwards compatibility. Usually that should not cause any changed behavior, but when starting the MariaDB server via systemd, or via the `mysqld_safe` script symlink, the server process will now always be started as `mariadbd`, not `mysqld`. Any 3rd party software or scripts looking for the `mysqld` name in the system process list must now look for `mariadbd` instead.

Normal MariaDB 10.6 introduced a new reserved word: OFFSET. This can no longer be used as an identifier without being quoted.

Normal From MariaDB 10.6, tables that are of the `COMPRESSED` row format are read-only by default. This is the first step towards removing write support and deprecating the feature. The `innodb_read_only_compressed` variable must be set to `OFF` in order to make the tables writable.

3 of them are Critical and 3 are Normal.

Is this going to be problematic for CMSB?