[BUGFIX] Move the Note Trails when moving a Held Note in the Chart Editor

[KoloInDaCrib]

Does this PR close any issues? If so, link them below.

#4120

Briefly describe the issue(s) fixed.

Essentially copied some code from the regular notes and applied it to note trails

Include any relevant screenshots or videos.

2025-02-09.15-20-39.mp4

[Lasercar]

Ah, I thought I might had to create a null hold note var and then pass a hold note when one is found. Nice work!

Also, you could probably remove that // TODO: Handle selection of hold notes. comment (unless it's for something else?).

[amyspark-ng]

i wonder why the editor handles things this way, im making a similar editor and all notes (regular, long and events) are something called stamps, with this all the behaviour is the same

at least make long notes and regular notes the same class, can't long notes just be a regular note that draws differently if length is not null?

[KoloInDaCrib]

i wonder why the editor handles things this way, im making a similar editor and all notes (regular, long and events) are something called stamps, with this all the behaviour is the same

at least make long notes and regular notes the same class, can't long notes just be a regular note that draws differently if length is not null?

SustainTrail uses the rendering system similar to FlxStrip, which is using triangles, vertices and similar to render the notes' graphic instead of rendering it normally like a regular FlxSprite. Granted it is possible to mix them into one class but I think that would've been less readable. Like back before 0.3 every util was using CoolUtil which was executed (rest in peace) in favour of the utils folder simply due to the fact that it's more readable, despite some utils not even being a 100 lines long excluding comments and therefore could've been easily bundled with other utils

[amyspark-ng]

so it's basically because the trail has different rendering method and readability?