Handle out-of-range DateTimeField values

[Oleg-Melnik]

Fixes #123.

Summary

• validate converted date-time instants against the Protobuf Timestamp range;
• report unsupported boundary values as normal field parsing errors;
• add deterministic lower-bound, upper-bound, and normal-value tests;
• bump Chords to 2.0.0-SNAPSHOT.92 and regenerate dependency reports.

Root cause

DateTimeField converted local input through the current zone offset and passed the resulting milliseconds to Timestamps.fromMillis(). Boundary values such as 0001-01-01 00:00 can fall outside Protobuf's supported UTC range after applying a positive offset, causing an IllegalArgumentException to escape the field parser.

Impact

Out-of-range date-time values now leave the field invalid with a clear validation message instead of triggering an unexpected-exception dialog. Valid date-time parsing and formatting remain unchanged.