Restoring from a mysqldump from older version makes mysql_upgrade version test fail

The mysql_upgrade tool uses a file $datadir/mariadb_upgrade_info to store what version it upgraded the servers system schema to, and checks against the version in that file to determine whether it needs to do anything when invoked again.

Yet when restoring a full mariadb-dump backup from an older versions server instance that older versions system schema gets restored, and would require to be upgraded by mariadb-upgrade once again. Yet the upgrade tool will just see the mariadb_upgrade_info file contents showing the current version number, and will so do not perform any actual schema upgrades unless explicitly started with --force.

The schema version information should not be stored directly in the file system, but rather in a system table so that it will be backed up and restored with the corresponding system schema change when using the mariadb-dump method for backup and restore, for obvious consistency reasons.

Also right now the mariadb_upgrade_info file is the only reason for only being able to run the upgrade tool locally AFAICT; everything else it can perform remotely via the client protocol?