PHASE 5 CLOCK-DOMAIN FIX (0.0.14.1)

Observed symptom
- Live meteor never appeared when testing with /phayriosis_phase_set 1 and /time set 168000.

Root cause
- Meteor minimum-day eligibility incorrectly compared meteorMinimumDay * 24000 against Level#getGameTime (SRG m_46467_).
- /time set changes Level#getDayTime (SRG m_46468_), not game time.
- Therefore admin time commands could not satisfy the day gate, and fresh worlds effectively had to run for seven real Minecraft days.

Correction
- Calendar/day eligibility now uses getDayTime / m_46468_.
- Retry/check intervals remain on getGameTime / m_46467_ so clock rewinds and /time set do not corrupt elapsed scheduler intervals.
- Event-data schema bumped to 3.0. Worlds carrying schema 1/2 stale timing are reset only when no meteor is pending/active.
- Existing pending/active events are preserved.
- Initial eligible roll is scheduled 20 game ticks after eligibility is recognized; ineligible state rechecks every 200 game ticks.

Important continuation rule
- Keep calendar thresholds and elapsed intervals in separate clock domains. Do not use gameTime to represent world day number.
