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
4 jobs for fix/drop_createDateTimeFromMillis in 0 seconds
Status Job ID Name Coverage
  External
passed ERP5.CodingStyleTest-TestRunner2

00:36:09

running ERP5.CodingStyleTest-TestRunner2

23512:01:45

failed ERP5.UnitTest-TestRunner2

01:02:07

running ERP5.UnitTest-TestRunner2

23512:01:02