TargetSolver: use simple date arithmetics instead of createDateTimeFromMillis

Maybe this made sense long time ago, but nowadays we are using
equivalence testers which tolerate date differences with more flexibility.

createDateTimeFromMillis was also problematic as it uses internal
private attributes of DateTime which is a pylint error with more recent
DateTime
6 jobs for display_stop_date_in_Event_view in 0 seconds
Status Job ID Name Coverage
  External
passed SlapOS.Eggs.UnitTest-Master.Python2

00:11:50

passed SlapOS.Eggs.UnitTest-Master.Python3

00:14:11

passed SlapOS.Eggs.UnitTest-Master.Python2

00:12:32

passed SlapOS.Eggs.UnitTest-Master.Python2

00:16:19

passed SlapOS.Eggs.UnitTest-Master.Python3

00:12:14

passed SlapOS.Eggs.UnitTest-Master.Python3

00:25:37