A timeZone configured scheduler should recognize time zone information from string date values

[JockeLindberg]

For example, setting startDate to '2024-02-09T10:00:00Z' will today, on a Scheduler configured with timeZone=0 (UTC) on a client with time zone +60 will result in startDate = '2024-02-09T11:00:00'. It should be 2024-02-09T10:00:00.

Reason for the current behaviour is that there is no time zone logic applied when setting a string date, just simple parsing into the local time zone.

Will probably need to override the setters for start- and enddates and apply some logic.

Forum post