Database setup for the Website service (#13)

This PR contains the work done to introduce a _Fluent_-based persistence layer for the Website service, selectable at runtime alongside the existing in-memory default, plus the local dev tooling and docs to support it.

To provide further details about the work:

* Persistence package
  * The `Driver` and `TLS` enumerations
  * The `Configuration` type
  * The `Service` factory that builds the  service
  * `PrepareDB` for migrations registration
  * The `Probe` for readiness checks.

* App integration
  *  Builds the driver, registers migrations, and attaches `Fluent` to the service lifecycle so it starts/stops with the HTTP server.
  * Migrate-on-boot is gated to the in-memory backend; MySQL/MariaDB is migrated out of band via --database-migrate so shared databases never race on startup.
  * The `ConfigReader+Properties` extension maps database.* config keys onto the driver.

* Library
  * Added database configuration constants.
  * The `HealthController` controller gains a readiness probe: `GET /health/ready` checks whether the database is reachable, separate from the existing liveness check.

* Others
  * Updated the `docker-compose` files to support a database service behind a database profile, and hardened for local development
  * New database targets on the `Makefile` file and overall documentation updated
  * Updated the `.env.local`, `Dockerfile`, and `README` files to document the persistence workflow, config keys, and local DB commands

Reviewed-on: rock-n-code/loud-amsterdam#13
Co-authored-by: Javier Cicchelli <javier@rock-n-code.com>
Co-committed-by: Javier Cicchelli <javier@rock-n-code.com>

Services/Website/docker-compose.override.yml

@@ -12,9 +12,42 @@ services:
     image: ${IMAGE_NAME}:${IMAGE_TAG:-latest}
     platform: linux/arm64
     build:
-      # The build context is the repo root so the local Localization package
-      # (referenced via ../../Packages/Localization) is inside the context.
       context: ../..
       dockerfile: Services/Website/Dockerfile
     environment:
       LOG_LEVEL: debug
+      DATABASE_DRIVER: ${DATABASE_DRIVER:-inMemory}
+      DATABASE_HOST: ${DATABASE_HOST:-localhost}
+      DATABASE_TLS: ${DATABASE_TLS:-off}
+
+  # Local development database, started only with the `database` profile so a plain
+  # `docker compose up` still runs the in-memory backend:
+  #
+  #   docker compose --profile database up mariadb
+  mariadb:
+    image: mariadb:11
+    container_name: ${HOST_OWNER:-loud}-db
+    restart: unless-stopped
+    profiles:
+      - database
+    ports:
+      - "127.0.0.1:${DATABASE_PORT:-3306}:3306"
+    environment:
+      MARIADB_RANDOM_ROOT_PASSWORD: "yes"
+      MARIADB_DATABASE: ${DATABASE_NAME:-loud-ams}
+      MARIADB_USER: ${DATABASE_USERNAME:-loud-ams}
+      MARIADB_PASSWORD: ${DATABASE_PASSWORD:-loud-ams}
+      MARIADB_AUTO_UPGRADE: "1"
+    command:
+      - "--character-set-server=utf8mb4"
+      - "--collation-server=utf8mb4_unicode_ci"
+    security_opt:
+      - no-new-privileges:true
+    healthcheck:
+      test: ["CMD", "healthcheck.sh", "--connect", "--innodb_initialized"]
+      interval: 5s
+      timeout: 5s
+      retries: 10
+      start_period: 30s
+    volumes:
+      - ./Tests/DB:/var/lib/mysql