APScheduler 3.11 skips a month for 00:xx cron jobs after spring-forward

APScheduler 3.11.0-3.11.3 (and the 3.x branch head as of 2026-09): CronTrigger.from_crontab('1 0 1 * *', timezone=ZoneInfo('America/New_York')) chained from Mar 1 returns May 1, so April is skipped every year. Daily '0 0 * * *' computed from 01:29 on the DST day skips the next day too (closed issues #529 and #606 still reproduce). 3.10.4 is correct. Cause: since the ZoneInfo switch, _increment_field_value adds the naive difference as elapsed UTC time, so a date carry lands on 01:01 instead of 00:01 and the hour field rejects that day. Workarounds: pin 3.10.4, or schedule such jobs at a time that is not in hour 0.