Fix Release workflow failure by building database/redis package images locally

[Copilot]

The Release job failed while publishing because the packaging step attempted to pull database.honcho.dnp.dappnode.eth:0.1.0, which is not published in a registry. This change makes database and redis first-class build services so release packaging no longer depends on external pulls for these internal runtime images.

• Root cause addressed

  • @dappnode/dappnodesdk publish treated database/redis as external images and attempted docker pull on package-tagged names that do not exist remotely.

• Compose changes

  • Added build contexts for database and redis in docker-compose.yml.
  • Kept runtime image references aligned with upstream bases.

• New minimal build contexts

  • Added database/Dockerfile:

    FROM pgvector/pgvector:pg15

  • Added redis/Dockerfile:

    FROM redis:7-alpine

• Resulting packaging behavior

  • database and redis are now built during package image build flow, avoiding the failing external pull path in the Release job.