[Bug]: macOS VFS Error and crash when restart

### ⚠️ Before submitting, please verify the following: ⚠️

- [x] This is a **bug**, not a question or a configuration issue.
- [x] This issue is **not** already reported on Github (I've searched it).
- [x] Nextcloud Server and Desktop Client are **up to date**. See [Server Maintenance and Release Schedule](https://github.com/nextcloud/server/wiki/Maintenance-and-Release-Schedule) and [Desktop Releases](https://nextcloud.com/install/#install-clients) for supported versions.
- [x] I agree to follow Nextcloud's [Code of Conduct](https://nextcloud.com/contribute/code-of-conduct/)

### Bug description

I'm using a M4pro MacBook with macOS v26.0.1.
The Nextcloud server uses a self-signed certificate.
So, I have to close HSTS to connect to the server.

However, when I connected to the server and continued to set folders, I selected the VFS option and clicked next. But, when I again opened the settings of the Nextcloud app, it showed that the VFS was closed. If I opened it, it would crash. The VFS folder in Finder showed that `"Nextcloud" is signed out.`

What's more, when I tried to solve this by restarting my computer, Nextcloud opened by itself when I logged in but crashed. I found this in the activity monitor. After force quitting and opening it again, it started but continually without VFS.

This is just the same issue which occurred in the version one year ago (maybe the version 1.15).

### Steps to reproduce

1. Install the Nextcloud app
2. Choose VFS for folder settings
3. Open the settings of the app and click VFS page
4. Go to Finder and click Nextcloud in side bar
5. Restart the Mac
6. Open activity monitor and find Nextcloud

### Expected behavior

The VFS should work normally.

### Which files are affected by this bug

All

### Operating system

macOS

### Which version of the operating system you are running.

V26.0.1

### Package

Official macOS Virtual files 12+ universal pkg

### Nextcloud Server version

32.0.0

### Nextcloud Desktop Client version

3.17.3

### Is this bug present after an update or on a fresh install?

Updated to a major version (ex. 3.16.3 to 3.17.0)

### Are you using the Nextcloud Server Encryption module?

Encryption is Disabled

### Are you using an external user-backend?

- [ ] Default internal user-backend
- [ ] LDAP/ Active Directory
- [ ] SSO - SAML
- [ ] Other

### Nextcloud Server logs

```shell

```

### Additional info

_No response_