fix(dav): apply client-provided mtime before cache update

[joshtrichards]

• Resolves: [Bug]: 32.0.5.0 (client 3.17.4) etag changes on unchanged file #58978

Summary

When a sync client uploads a file with an x-oc-mtime header, the provided mtime is applied after $storage->getUpdater()->update() runs. The scanner inside update() reads the filesystem mtime via stat(), which at that point reflects the current server time -- not the client-provided value. This means the cache is briefly populated with the wrong mtime before View::touch() corrects it.

Additionally, View::touch() goes through basicOperation, which can trigger writeUpdate() hooks/updater side effects depending on the view's state -- an unnecessary risk given the DAV code already manages the updater manually.

Changes introduced by this PR:

• Call $storage->touch($internalPath, $mtime) before the updater, so the scanner sees the correct mtime from the filesystem.
• If the native touch fails (some backends don't support it), write mtime directly to the filecache via putFileInfo.
  • This is essentially what the existing implementation did; we should perhaps document that behavior could still be problematic on storage backends that don't support it
• Consolidate upload_time, mtime (fallback), and creation_time into a single putFileInfo call.
• Remove the View::touch() call entirely.

TODO

• Test
• Decide whether to backport or not (I vote yes, but...)

Checklist

• Code is properly formatted
• Sign-off message is added to all commits
• Tests (unit, integration, api and/or acceptance) are included
• Screenshots before/after for front-end changes
• Documentation (manuals or wiki) has been updated or is not required
• Backports requested where applicable (ex: critical bugfixes)
• Labels added where applicable (ex: bug/enhancement, 3. to review, feature component)
• Milestone added for target branch/version (ex: 32.x for stable32)

AI (if applicable)

• The content of this PR was partly or fully generated using AI