Fix historical SQL timestamp conversion

[Evolvion]

Problem

Valid timestamps such as 0001-01-01 could be converted to year zero through legacy Java calendar handling, then rejected by midPoint's XML date parser.

Fix and rationale

• Pre-1900 calendar fields are preserved as UTC on reads, writes, and filters. Historical timezone offsets are deliberately ignored; this limitation is documented in code.
• 1900 was selected as a practical cutoff, not a technical requirement. The fix is kept small for uncommon historical dates, without a calendar/timezone redesign.
• Conversion from 1900 onward, including 9999, is left unchanged. Date-only and timezone-aware mappings are also unchanged.

Testing

• 484 default tests were run successfully with mvn -o -B test.
• Boundary dates, XML validity, round-trips, and filter parameters are covered, with conversion checks in UTC and Europe/Bratislava.
• Oracle parameter binding and Prism conversion were checked separately.