Bug: Nextcloud client triggers ASP.NET restarts due to unexpected file modifications

**Description**
After updating to **Nextcloud Desktop Client 3.16.5**, I started experiencing unexpected application domain (AppDomain) restarts while debugging ASP.NET Web Forms projects in Visual Studio.

This happens even without any code changes — the ASP.NET runtime detects changes in watched files and restarts the application, which causes loss of session state during debugging.

This behavior was not present before updating the client, and it seems like the new version is altering file metadata or triggering filesystem events unnecessarily.

**Environment**
- Nextcloud Desktop Client: **3.16.5**
- OS: **Windows 11 24H2**
- IDE: **Visual Studio 2022 Professional 64-bit – Version 17.14.0**
- Project type: **ASP.NET Web Forms (.NET Framework)**

**Steps to reproduce**
1. Install Nextcloud client and sync a folder containing multiple Visual Studio projects (e.g., `C:\Sorgenti`)
2. Start debugging an ASP.NET project
3. Leave the app running, make a small edit (e.g. .aspx page)
4. Notice that the application restarts and the session is lost — even though no real change to the underlying source files was made

**Expected behavior**
Nextcloud should not trigger file change events unless actual content has changed.

**Actual behavior**
The client appears to be touching or re-writing metadata of some files, which causes ASP.NET to detect changes and recycle the AppDomain.

**Workaround**
Temporarily disabling the Nextcloud client resolves the issue.
A long-term workaround is to work in a folder outside of the sync path and sync manually at the end of the day.

**Additional context**
This problem started only after upgrading to 3.16.5. Many developers working with Visual Studio and Nextcloud may be affected without realizing it. It could be related to new background indexing or modified timestamp handling in this version.

Please investigate, as this makes the client disruptive to common .NET development workflows.