Way to persistently block application from hydrating files on stat

### How to use GitHub

* Please use the 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to show that you are interested into the same feature.
* Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
* Subscribe to receive notifications on status change and new comments.

---

## Feature request

32.0.1 / Windows client 4.0.1

**Is your feature request related to a problem? Please describe.**
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

I have a large virtual Nextcloud filesystem, and would like to keep most of it dehydrated. When searching for files (by name / metadata) with "find" in git-bash, the Nextcloud client appears to attempt hydrating all files.

**Describe the solution you'd like**
A clear and concise description of what you want to happen.

Ideally it would be possible to identify that the file is not being "opened" as such, but presumably polled for metadata.

Currently, if I need to run a query such as:

find . -type d -empty
(e.g. yes, I did run Client version 4.0.0 recently!), I am hitting "Block app" on the pop-up that appears in the system notifications. "find" continues to work successfully.

Unfortunately, the block does not appear to be persistent, and running the command a second time still results in more attempts to hydrate my virtual files.

**Describe alternatives you've considered**
A clear and concise description of any alternative solutions or features you've considered.

(Possibly a patch to "find" to make it not stat everything? - But ideally Nextcloud Client would either let me block this behavior persistently for this program, OR - possibly wait until the file is opened to trigger the hydration?

**Additional context**
Add any other context or screenshots about the feature request here.