DragOperation.position.current is one "frame" behind when using Keyboard navigation

I use the following logic to get the relative position of the dragged element relative to the current drop target:
```
const dragPositionRelativeToTarget = position.current.y < target.shape.center.y ? 'top' : 'bottom';
```

This works fine with mouse sensor, but when using keyboard sensor the value of `position.current.y` is from the "previous key press". Lets assume the following sequence: Up/Up/Down/Down then the first Down is still registered as Up and the `position.current.y` decreases. Edit: The actual position of the DragOverlay is updated correctly though.

Reproduce the issue in the dnd-kit drag operation with the keyboard sensor using the Up/Up/Down/Down sequence, then trace where DragOperation.position.current is updated. Confirm that position.current.y reflects the latest key press while the DragOverlay remains correctly positioned.

Written by the indexing model from the issue text.