fix: validate epoch-ms range before converting int64 date columns

fix: validate epoch-ms range before converting int64 date columns

Reject int64 values outside [2010, 2035] epoch-ms range to fail fast
on corrupted data instead of silently producing wrong dates. Catches
nanosecond/microsecond values that would pass the int64 dtype check
but produce garbage timestamps if interpreted as milliseconds.