YADE - KeepModificationDate is broken for atomic transfers

Current Situation

• If TargetFileOptions->KeepModificationDate is set to true/false then:
  • The KeepModificationDate information is not visible in the YADE banner output.
• If YADE is configured for an atomic transfer (e.g. Transactional=true) and TargetFileOptions->KeepModificationDate is set to true then:
  • YADE tried to set the modification date not to the transferred file (e.g. with the suffix ~), but to the original file name.
    • If this file (original file name) does not exist on the target host:
      • The Local provider does not log error messages.
      • Other providers report an error message that a file was not found.
    • If this file exist:
      • All providers set the modification date for this file.
      • However, after the atomic rename, the file is overwritten and the modification date is lost.