Selection is lost when a HitObject is moved to another playfield when using pooling

[LumpBloom7]

Describe the bug:
When handling a movement within the selection handler, if the resulting position leads to the HitObject changing playfields, the HitObject is deselected, requiring users to reselect and repeat to move further.

Problem encountered in the sentakki ruleset, the lane in LanedHitObject is handled similarly to columns in ManiaHitObject.
https://github.com/LumpBloom7/sentakki/blob/Editor/osu.Game.Rulesets.Sentakki/Edit/SentakkiSelectionHandler.cs#L26-L50

A half-workaround that I did manage to find is to remove the HO from EditorBeatmap.SelectedHitObjects, then readding it after the lane has been changed. This ensures the SelectionBlueprint is shown, but still won't continue responding to the current drag event.

Screenshots or videos showing encountered issue:

2021-01-10.16-46-29.mp4

osu!lazer version:
2021.109.0

Logs:
N/A

[peppy]

I guess we haven't encountered this yet because mania doesn't use pooling. I think this will likely be addressed along with the mania pooling implementation in the coming month or two.