ConflictResolver: initialize mTimeFrameConstraint with valid KDateTime

The API later on only changes date or time part of the KDateTime, but
that still does not make the KDateTime valid, since it was originally
invalid and nothing has set the timeSpec. This actually makes scheduling
based on FreeBusy information work again.