locking a received share that was moved in a folder does not lock the main folder

[individual-it]

Steps to reproduce

1. receive a shared file
2. move the file in a self created folder
3. lock the file
4. delete the folder

Expected behaviour

it should not be possible to delete or rename the folder

Actual behaviour

user can delete and rename the containing folder
if the folder contains an item owned by the user itself deleting or renaming the containing folder would not be possible

[PVince81]

since it's a mount point, the "get locks from all children" on deletion might not find it

[PVince81]

moving to backlog as not critical: the received file/folder will continue to exist at the owner's despite deletion.

keeping open because the lock is expected to work because in other tickets we decided that locks expand beside mount points, like #33847

[ownclouders]

GitMate.io thinks possibly related issues are #12762 ([master] Moving encrypted shared folder doesn't move keys properly), #34369 (locking root of DAV does not look received shares), #17243 (Lock sharing operations when file is locked), #14094 (Tipsy does not close on shared folder), and #27500 (Cannot move received internal share into folder shared as link).