Upgrade

[nemchik]

• Use the mariadb specific commands (ex: mysqladmin is a symlink to mariadb-admin)
• Document information about upgrading the database using mariadb-upgrade
• Add logic after svc-mariadb to check if an upgrade is required and notify the user in logs

[LinuxServer-CI]

I am a bot, here are the test results for this PR: https://ci-tests.linuxserver.io/lspipepr/mariadb/10.6.10-r0-pkg-42d0487d-pr-112/index.html https://ci-tests.linuxserver.io/lspipepr/mariadb/10.6.10-r0-pkg-42d0487d-pr-112/shellcheck-result.xml

[github-actions[bot]]

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[LinuxServer-CI]

I am a bot, here are the test results for this PR: https://ci-tests.linuxserver.io/lspipepr/mariadb/10.6.10-r0-pkg-59050081-pr-112/index.html https://ci-tests.linuxserver.io/lspipepr/mariadb/10.6.10-r0-pkg-59050081-pr-112/shellcheck-result.xml

[LinuxServer-CI]

I am a bot, here are the test results for this PR: https://ci-tests.linuxserver.io/lspipepr/mariadb/10.6.10-r0-pkg-59050081-pr-112/index.html https://ci-tests.linuxserver.io/lspipepr/mariadb/10.6.10-r0-pkg-59050081-pr-112/shellcheck-result.xml

[nemchik]

Reworked to have the upgrade check run after svc-mariadb is ready. It is also now completely silent unless an upgrade is needed (and the MYSQL_ROOT_PASSWORD variable contains a valid root password).

The issue with the initial attempt was the upgrade logic being wedged into the initdb logic and trying to start mariadb without a password in order to then check if an upgrade was needed.

I have tested lspipepr/mariadb:amd64-10.6.10-r0-pkg-59050081-pr-112 and confirmed it works as expected.

[LinuxServer-CI]

I am a bot, here are the test results for this PR: https://ci-tests.linuxserver.io/lspipepr/mariadb/10.6.10-r0-pkg-59050081-pr-112/index.html https://ci-tests.linuxserver.io/lspipepr/mariadb/10.6.10-r0-pkg-59050081-pr-112/shellcheck-result.xml