fix(deploy): pin to :1.4.0 (the :1.4.1 GHCR tag never published)

The docker-publish workflow's run for the v1.4.1 tag reported success
in GH Actions, but no `1.4.1` tag landed on the ghcr.io registry
(`docker pull ghcr.io/mbombeck/healthlog:1.4.1` returns 'manifest
unknown'). Coolify tries to pull, fails, and never replaces the old
container — so the site stays 503 with no upstream at all.

Repinned to `:1.4.0` which is verifiably present on GHCR (2h old).
Healthcheck fix from the previous commit (127.0.0.1) stays.

The :1.4.1 publish failure is a separate followup — likely related
to the docker-publish workflow not handling the squash-merge release
flow correctly for the tag-on-main scenario. Tracked for v1.4.2.

docker-compose.yml

@@ -9,7 +9,7 @@ services:
     # to the last release that's verifiably running on self-host installs to
     # rule out runtime / Docker-network issues. No `build:` block on purpose:
     # we want Coolify to PULL the prebuilt image, not build from source.
-    image: ghcr.io/mbombeck/healthlog:1.4.1
+    image: ghcr.io/mbombeck/healthlog:1.4.0
     container_name: healthlog-app
     ports:
       - "3000:3000"