Deployment should consider the take over of a locked folder

Current Situation

When a folder is locked by a user 1 and will be taken over by user 2 then the deployment in the inventory editor will cause an entry in the deployment report: Folder is locked by other user. This occurs }}even if  user 2 has taken over the folder.

Desired Behavior

When a user takes over a folder this should be considered during the deployment.

Maintainer Notes

• Consider the underlying wording for locking objects and for deploying objects:
  • Editorship: when an object is edited then its folder will be locked for the current user and ownership is handed over to the current user.
  • Ownership: when an object is deployed then by default only objects owned by the current user can be deployed.
• Deployment works independently from editorship, i.e. it does not consider locks owned by other users, but ownership for the object.
  • When deploying a number of objects with the "Deploy" button then the current user has a choice to deploy only objects owned by himself (default) or to deploy objects owned by any users. The second option has to be used to deploy on behalf of other users.
  • When deploying an individual object with the "Deploy" action menu of the object then this will deploy the object only if it is owned by the current user. When trying to deploy from the action menu an object owned by a different user then the deployment will fail and the deployment report will include a message stating this fact. In previous releases the message for this situation was wrong. Starting from release 1.13.3 the error message has been updated to state: Object is owned by other user.