v0.6.4-beta: Alembic Logging Config Hotfix

[DeepZone]

Motivation

• Alembic CLI commands crashed with KeyError: 'formatters' when backend/alembic/env.py called fileConfig(...) against a minimal backend/alembic.ini that lacked logging sections.
• The intent is to make Alembic migration commands reliable in containerized/dev setups without changing any routing/domain logic or performing any DB/RIPE/ROA writes.

Description

• Hardened backend/alembic/env.py by adding a _configure_logging() helper that uses pathlib.Path and configparser to call fileConfig(...) only if config.config_file_name exists and contains the sections loggers, handlers, and formatters.
• Added default logging sections to backend/alembic.ini (loggers/handlers/formatters + console handler and generic formatter) so Alembic CLI works with the traditional fileConfig flow.
• Updated operational docs to show Docker-based Alembic commands (docker compose exec backend alembic current, ... heads, ... upgrade head) and added a troubleshooting entry for KeyError: 'formatters' with the recommended fix to upgrade to this release.
• Bumped user-facing version to v0.6.4-beta and runtime/package versions to 0.6.4 across backend and frontend artifacts, and updated RELEASE_NOTES.md with the hotfix entry.

Testing

• Ran backend unit tests: cd backend && pytest -q — tests passed (83 passed).
• Built frontend: cd frontend && npm run build — build succeeded.
• Attempted to validate Alembic CLI inside Docker (docker compose exec backend alembic current) but the environment does not provide Docker (docker: command not found), so runtime Docker verification was not executed here.

---

Codex Task