Improve release timing on matomo docker images for new versions

Nobody has claimed this yet.

Hello,

Please synchronize the new version that is upgrade-able in Matomo website with the docker image release. Matomo will upgrade automatically to the latest version if you run the core:upgrade command, but then we are not able to also upgrade the docker image, as there is a big delay between the release on matomo and the docker release. So we can't scale up matomo, as old binaries will not work on the new version of the database. And if the docker container where you ran the upgrade command is deleted, you are left with no working matomo containers.

There are sometimes over a week between the 2 releases, period in which we can't upgrade Matomo if we are using docker images. This is even more important when a release is a CRITICAL SECURITY FIX, as timing matters.

Thank you
Valentina

No files or tests are named. Start by tracing how Matomo website releases reach the Docker image publishing workflow, and compare that with the core:upgrade version source. Done means newly released Matomo versions, especially critical security fixes, become available as Docker images without the current week-long delay.

Written by the indexing model from the issue text.