[Bug]: E2EE - Secure file drop does not sync when file drop folder is not at the root level

### ⚠️ 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

When creating a secure file drop link at the second level of the folder tree or below, the uploaded files are not synced, effectively making the secure drop area useless. Please note that for the user who uploads the operation seems to be successful.

Experienced on c.nc.com

### Steps to reproduce

1. Create an encrypted folder at the second level of your folder tree or below (that is not at root level)
2. Create a secure file drop link
3. Upload a file using that link

### Expected behavior

The file is synced in the Desktop Client.

### Which files are affected by this bug

secure file drop

### Operating system

Linux

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

Ubuntu Desktop 22.04

### Package

Distro package manager

### Nextcloud Server version

c.nc.c

### Nextcloud Desktop Client version

3.9.1

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

Updated from a minor version (ex. 3.4.2 to 3.4.4)

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

Encryption is Enabled

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

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

### Nextcloud Server logs

_No response_

### Additional info

_No response_