Add openhabittracker template

[Jinjinov]

What is this PR about?

New template: OpenHabitTracker - a free, open source (GPL-3.0) app to take notes, plan tasks, and track habits. The Docker image is a self-hosted single-user sync server that the native apps and web app log into; all data stays on the server. REST API with a Scalar UI at /scalar/v1.

Adds blueprints/openhabittracker/ (docker-compose.yml, template.toml, meta.json, openhabittracker.png).

• Image jinjinov/openhabittracker:latest (multi-arch amd64 + arm64).
• template.toml uses a [config.env] table of named vars referenced as ${NAME} in the compose (tolgee / gitea-sqlite idiom); admin password ${password:24} and JWT secret ${base64:48} are generated by Dokploy, nothing hardcoded. Domain routes to internal port 8080 via [[config.domains]].

Checklist

• I have read the suggestions in the README (general requirements)
• I have tested the template in my instance (see Testing - validated at container + metadata level; no self-hosted Dokploy instance, the PR auto-preview will exercise the full deploy)
• No unit tests apply to a template blueprint

Testing

• node build-scripts/generate-meta.js --check passes (477 templates validated, incl. this one).
• Ran the image with the template's environment: container came up healthy, EF migrations applied cleanly, login page returned HTTP 200.
• template.toml env wiring mirrors the live tolgee and gitea-sqlite blueprints exactly.

[github-actions]

built with Refined Cloudflare Pages Action

⚡ Cloudflare Pages Deployment

Name	Status	Preview	Last Commit
templates	✅ Ready (View Log)	Visit Preview	6d56faf

[Siumauricio]

Tested this template on a live Dokploy instance — works out of the box. ✅

Deploy evidence:

• Compose service created from the PR branch as-is, deploy finished in ~10s.
• GET / → 302 → /login → HTTP 200 with <title>OpenHabitTracker</title> (Blazor Server on Kestrel), served through the Dokploy-generated domain on internal port 8080.
• Dokploy-generated ${password:24} admin password and ${base64:48} JWT secret were accepted by the app; EF migrations ran cleanly on the fresh volume.
• /scalar/v1 correctly returns 401 without auth.

Checks:

• node build-scripts/generate-meta.js --check passes (477 templates).
• No container_name, no fixed host ports, no external network — follows repo conventions.
• Per-template meta.json with id matching the folder, 512x512 PNG logo included.
• Image jinjinov/openhabittracker:latest is multi-arch (amd64 + arm64), published by the upstream maintainer.

LGTM.