Event-driven world time sync (timeSync flag)

Introduce an optional timeSync field and event-driven time pushes so host time is only re-applied on connect, resume-from-freeze, or large jumps while weather continues on ~1 Hz heartbeats. Added IsGameTimeFrozen detection and client buffering of latest host time; clients apply host time only when timeSync is true or when gameplay just resumed. Updated networking to read/write timeSync, adjusted F4TWorldStateSync logic (separate time vs weather send/apply paths, changed function signatures and behavior), and updated protocol/docs/changelog and fake_client logging to reflect the new field and behavior.

server/fake_client.py

@@ -73,6 +73,7 @@ def update_host_world_state(packet: dict[str, Any]) -> None:
         "gameHour": get_optional_game_time(packet, "gameHour"),
         "gameDaysPassed": get_optional_game_time(packet, "gameDaysPassed"),
         "weatherFormId": packet.get("weatherFormId", ""),
+        "timeSync": packet.get("timeSync", False),
         "clientTime": packet.get("clientTime", 0.0),
         "serverTime": packet.get("serverTime", 0.0),
         "lastReceivedLocalTime": time.time(),
@@ -93,6 +94,7 @@ def print_host_world_state(world_state: dict[str, Any]) -> None:
                 f"Game Hour: {world_state['gameHour']:.3f}",
                 f"Game Days Passed: {world_state['gameDaysPassed']:.3f}",
                 f"Weather Form ID: {weather_form_id}",
+                f"Time Sync: {world_state.get('timeSync', False)}",
                 f"Client Time: {client_time}",
                 f"Last Server Time: {server_time}",
                 f"Last Received Local Time: {world_state['lastReceivedLocalTime']}",