fix(self-hosting): run database migrations in Coolify deployment (#2621) master
* fix(self-hosting): run database migrations in Coolify deployment coolify-deployment.yaml relied on prebuilt GHCR images but never ran schema migrations, so fresh deployments started with an empty database and sign-in failed with LibsqlError on the user table (#2532). - publish the one-shot migration runner (packages/db/Dockerfile) as ghcr.io/openstatushq/openstatus-db-migrate via docker-publish.yml - add a db-migrate service to coolify-deployment.yaml and gate the app services on its completion - document that migrations run automatically on every deploy * ci: drop dead db-migrate entry from per-app change detection db-migrate lives under packages/db/, so the apps/<service>/ grep in the else branch can never match it; its builds are triggered by the packages/** path above.