Deletion of a Set of Inventory Objects should delete File Order Sources first

Current Situation

When a set of deployable Inventory Objects, containing at least one File Order Source and the workflow that is referenced, should be deleted from a controller the completed process will fail. The File Order Sources will be marked for deletion, but are still present until an agent has confirmed the deletion. Items still referenced by the file order sources that are marked for deletion cannot be deleted until the file order source is gone from the agent. 

Desired Behavior

• When a Set of inventory Objects should be deleted from a controller, all File Order Sources should be deleted first in a single commit.
• If the controller confirms, that the commit was successful (File Order Source is only Marked For Deletion), the JOC api checks the controller status recurringly if the File Order Sources is still present. (every 200ms, up to max 2s)
• the JOC api sends a second delete commit to the controller with all other items of the initial Set, either if the File Order Sources are finally deleted or after a timeout (2s)
• if the File Order Sources are not deleted in time
  • the second commit will still fail due to the workflow being still referenced by the still present File Order Source
  • the JOC api updates the optimistically stored Dep History Entries of the second commit with the given error messages. but not the File Order Sources from the successful first commit
  • the JOC api restores the optimistically removed items from the Trash, including the File Order Sources