Wrong isLocked flag when folder is locked

[Corepex]

I noticed that the API returns the wrong isLocked state in the /api/assets/tree endpoint.

Steps to reproduce

• Follow the description in Lock and propagate to children does not work studio-ui-bundle#962 to lock and propagate any folder.
• Request all items in the locked folder from /api/assets/tree
• check the isLocked flag

[mattamon]

I checked the problem and as it seems, the locking mechanismn, does not trigger the GDI

Is there a specific reason to use PATCH instead of the PUT endpoint?

[lukmzig]

As you can see for example for data objects here:
https://github.com/pimcore/pimcore/blob/12.x/models/DataObject/AbstractObject/Dao.php#L427

We will need to re-think the approach. When we set propagate on an item, the children elements are always looking for the parent, so no value is set on them. This will not work with the current GDI implementation.

Unlock propagate will probably have a similar issue.