fix(validation): throw ValidationError not RangeError on invalid date comparison

[devteamaegis]

What's broken

The dateGte / dateLte validators throw an uncaught RangeError: Invalid time value instead of a ValidationError when the configured comparison date is unparseable. A validator should only ever throw ValidationError, so this leaks a raw RangeError up the stack. Hit it by configuring a field with a malformed rule like dateGte:garbage (e.g. a typo in the Headless CMS model editor) — every submission to that field then 500s.

Why it happens

When the comparison value can't be parsed, new Date(value) is an Invalid Date. The comparison is false, so control enters the error branch, which builds the message with gteDate.toISOString() — and toISOString() on an Invalid Date throws RangeError. The validator crashes while trying to report a validation failure.

Fix

Guard with isNaN(date.getTime()) and throw a clear ValidationError when the comparison date is invalid.

Test

Added a case to each validator asserting a ValidationError (not RangeError) on a malformed comparison date; valid in-range/out-of-range behavior is unchanged.