BUG: Partial publish only the deletion of a Node but node descendant Node moves

[mhsdesign]

Steps to reproduce:

1. Cut a content element on Page A in a nested content collection like a slider: (main/slider)
2. Paste (which is move) the content element to Page B (main/slider)
3. Delete the content collection slider on Page A (main/slider)
4. Publish individually on PageA the removal

Expected:

The removal is either published and the moved node preserved in the remaining changes
or the editor is explained to that this is not possible.

Actual:

Beta15
As the step 2 cannot be applied on the users workspace as remaining events because the Node was indirectly deleted first due to the attempted publish of the removal 3. The conflict resolution will show up - thinking its a synchronisation problem with live - and tell that the move is not applicable and propose to drop it. But because a Rebase(force) is issued, which does nothing in this case as we are up to date nothing is dropped and the dialog will show up again.

Beta13
There is a chances it behaves differently from Beta15 and the move node WAS possible afterwards as the deletion of nodes was not correct until: #5320

So similarly to #5352 we would have events in the wrong order stating to now move a node while it was deleted first.

Ideas to fix

Improve the conflict resolution so in case the workspace is up to date AND the remaining events were not applicable tell the user that the change cannot be published as is but needs the move node as well.