fix: don't propagate future mtimes

[icewind1991]

When uploading a file with an mtime in the future the parent folders also get the future timestamp.

This clamps the propagated mtime to the current one to prevent this.

to test:

• create a local file with a timestamp in the future: touch -d "now +1 year" test.txt
• Create a folder test
• Upload test.txt into the test folder
• Check the mtime of the test folder

[icewind1991]

reverted the constructor argument changes, was causing to much splash damage

[icewind1991]

/backport to stable30

[icewind1991]

/backport to stable29

[Altahrim]

reverted the constructor argument changes, was causing to much splash damage

I didn't saw the "splash", do you think we could backport this and add clock in constructor for master?