feat(daytime): follow the real wall clock in the lobby

[TheMeinerLP]

Summary

New column features/daytime: the lobby time follows the wall clock of daytime.zone (default Europe/Berlin) linearly (06:00 -> 0, 12:00 -> 6000, 18:00 -> 12000, 00:00 -> 18000). It is updated once per second via the Minestom scheduler, and Minestom's own day cycle is stopped with defaultClock().rate(0f).

Configuration

• daytime.enabled: kill switch; when off, the lobby goes back to midday (6000).
• daytime.zone: the time zone the clock is read in.

Both are read on every run, so they apply live with the avaje-config watcher. An invalid zone aborts startup and names daytime.zone; at runtime the last valid zone is kept and a warning is logged once.

Notes

• MapProvider's midday freeze stays as the fallback for variants without the column; no bean ordering is needed.
• Supersedes feat: run the lobby on real Berlin time and seasons (Stage 2) #217: only the linear real-time part is rebuilt as a column. Seasons, the solar strategy, time.json and the strategy interfaces are deliberately out of scope (a solar mapping could follow as a separate feat). feat: run the lobby on real Berlin time and seasons (Stage 2) #217 will be closed with a reference once this is merged.
• OpenSpec change: openspec/changes/realtime-lobby-daytime (capability lobby-daytime).

Tests

• 36 tests in :features:daytime: DayTimeMappingTest (unit, including both Berlin DST transitions), DaytimeModuleTest (Cyano Env, adjustable Clock, env.tick()), ColumnArchitectureTest.
• ./gradlew build is green.
• Verified manually on the local variant: a live zone switch (Los Angeles night, Tokyo sunset) takes effect without restart.

https://claude.ai/code/session_01A7aAe2E6wAEbi6jjnyPTWH

[github-actions]

Test results

  222 files  222 suites   15m 18s ⏱️
  334 tests 333 ✅ 1 💤 0 ❌
1 002 runs  999 ✅ 3 💤 0 ❌

Results for commit f7014e9.