fix: raise ValueError for an out-of-range epoch in to_datetime

[eeshsaxena]

to_datetime (and therefore to_timestamp/to_date) leaks OverflowError/OSError on a number-like value that is out of range, instead of the ValueError it documents:

from sqlmesh.utils.date import to_datetime

to_datetime("inf")                    # OverflowError: timestamp out of range for platform time_t
to_datetime("1e30")                   # OverflowError
to_datetime("99999999999999999999")  # OSError: [Errno 22] Invalid argument

In the number branch, the value passes float() (float("inf") and large floats do not raise), strptime fails, and datetime.fromtimestamp(epoch / 1000.0) then overflows. Only ValueError was expected there, so OverflowError/OSError escape. The docstring states 'Raises: ValueError if value cannot be converted to a datetime', and "nan" already raises ValueError via the same path, so this makes the out-of-range cases consistent.

The fix catches OverflowError/OSError/ValueError around fromtimestamp and falls through to the existing raise ValueError(...). Added a parametrized regression test in tests/utils/test_date.py.