WBS is wrong after cut/paste when orderedParentIndex is persisted

[bmblb]

Steps to reproduce on advanced demo:

1. make orderedParentIndex persistable
2. enable useOrderedTreeForWbs and set wbsMode to auto
3. enable transactional features
4. use this dataset:

{
  "success": true,
  "tasks": {
    "rows": [
      {
        "id": 1,
        "name": "Parent",
        "expanded": true,
        "children": [
          {
            "id": 11,
            "name": "A",
            "duration": 8
          },
          {
            "id": 12,
            "name": "B",
            "duration": 5
          },
          {
            "id": 13,
            "name": "C",
            "duration": 2
          },
          {
            "id": 14,
            "name": "D",
            "duration": 3
          },
          {
            "id": 15,
            "name": "E",
            "duration": 4
          }
        ]
      }
    ]
  }
}

5. run demo, sort duration column in a descending order
6. cut task A (wbs 1.1), paste it below task E (wbs 1.5)

Expectation:
task A get wbs 1.5, task E get wbs 1.4
Behavior:
task A get wbs 1.4, task E get wbs 1.5

Visual position is correct in both cases.