v2.0.1

Fix Dokploy build and startup failures with Railpack 0.15.4.

• Remove the literal ... from buildAptPackages, which caused unrelated APT dependency conflicts.
• Use structured build commands so Railpack's shell quoting preserves the linker flags, application package, and output path. Require an executable out before the build succeeds.
• Explicitly copy the Go source directories and embedded OpenAPI files. Railpack's handling of .dockerignore negations otherwise removed nested sources and failed with stat /app/cmd/tt-scrap: directory not found.
• Add a CI job using the same Railpack 0.15.4 BuildKit frontend as Dokploy, followed by a check of the image's default startup command.
• Preserve the native HEIF codecs and Docker build allowlist, and document the Railpack configuration requirements.

Validation: reproduced the missing-source failure in a complete Railpack container build, then successfully built the corrected image through the Railpack 0.15.4 frontend. The resulting image's default startup command launched the application and reached its expected missing-API-key validation in an isolated, network-disabled test. The image contains the executable and all linked native libraries, without local .env or Git metadata. Earlier validation also passed the CGO application build and media tests. Production database initialization and upstream services were not exercised by the image smoke test.

This release and tag were recreated to include all three deployment fixes and the CI check.

Full changes since v2.0.0