[Bug]: mtime and etag propagate changes to parent when a file cannot be opened #65167

Description

When a file cannot be opened, but it exists on the filecache, the mtime and etag get updated and propagated to all parent directories up to the user's root. This causes unnecessary work as sync clients would see the difference and try to update their state, although no changes may have been done/detected.

This is especially noticeable when trying to download files via the ZipFolderPlugin as it triggers the issue consistently every time this failure happens on the storage.

How to reproduce

1. Log in as alice
2. Create a directory test
3. Create a file inside test named foobar.md
4. Make the file unreadable by the www-data process (e.g. chmod 000)
5. Check the 'Modified' column for test and notice when it was last updated
6. GET the foobad.md file
7. The request should fail, as the file cannot be opened
8. Check the Modified column for test
9. Notice that it was last updated a few seconds ago
10. Apply this fix
11. Perform step 6 to 8 again
12. Notice that the last updated time did not change