Bug: moving multiple content nodes results in wrong order

[bielerj]

Related to #3040

Description

If you move multiple content nodes the order of the copied content nodes can be reversed. (Given you selected the nodes from top to bottom)

Steps to Reproduce

1. Select two nodes from top to bottom
2. Move the selected nodes after a third node

Expected behavior

The two selected nodes are moved after the third node and keep their order.

Actual behavior

Before move:

After move:

The two selected nodes appear in reversed order after moveAfter.

Affected Versions

Neos: Tested in 8.1, probably <=8.3

UI: Tested in 8.1, probably <=8.3

[bielerj]

Workaround for editors: select nodes in bottom to top order when moving after or top to bottom order when moving before.