[Chore] Resolve penguin-dal version skew (manager 0.2.0 vs dns-server 0.3.0)

[PenguinzTech]

Problem

penguin-dal versions differ across services:

• manager/backend: penguin-dal==0.2.0
• dns-server: penguin-dal==0.3.0 (requires Python 3.13)

Both container images build on python:3.13. The shared dns-server app/services features (cert_manager, selective_dns_routing) run under 0.3.0 in production but are exercised in tests under the manager venv (Python 3.12 / penguin-dal 0.2.0) — a test-vs-prod version fidelity gap. The local host only has Python 3.12, so 0.3.0 could not be validated for the manager here.

Fix

1. Align both services on the same penguin-dal line (target 0.3.0 per the Python 3.13 standard).
2. Run the manager + dns-server acceptance suites under Python 3.13 / penguin-dal 0.3.0 (CI or a python:3.13 container) and confirm green before bumping the manager pin.
3. Ideally run the dns-server/tests_full_future acceptance suite under a single 3.13 venv that has both penguin-dal and hypercorn, removing the current venv split.

Context

Surfaced during the enterprise-hardening consolidation (PR #50). Low risk (penguin-dal is pyDAL-compatible; the insert/select/update/commit/close patterns used are stable), but should be verified on 3.13.