[BUG] "inside" and "outside" brushstrokes can sometimes get fully erased if you erase around it

[BaronAWC]

Describe the bug
There is an inconsistent bug where if you erase around a brushstroke that was just created with "inside" or "outside" mode, the stroke can get fully deleted.

To reproduce
Steps to reproduce the behavior:

1. create a brushstroke in "inside" or "outside" mode
2. erase around the path without touching the path
3. sometimes, the path will delete

Expected behavior
The path does not erase at all.

Screenshots
https://github.com/user-attachments/assets/26d8c535-ac98-441d-a7b5-5859d5ea486e

Editor version
Reproduced in Wick 1.19.4, Candlestick 1.0.1, and StickmanRed's PR that fixed the brush modes (so it's not a new bug at least).

[StickmanRed]

After doing some testing I think the path isn't deleting, but it becomes invisible by the fillColor being set to null (they can be selected by box select)

[StickmanRed]

When erasing an "inside" or "outside" brushstroke with multiple parts (a CompoundPath), the code flips the direction of the child paths somehow. I couldn't find out why. So the erase code eventually gets to this section, which handles leftover counter-clockwise paths. It turns them into clockwise regular paths, but it doesn't seem to set a fillColor for them. So null fillColor child paths keep their fill color

Possible solution:

        // ...
        }).forEach(hole => {
            hole.clockwise = !hole.clockwise;
            hole.fillColor = compoundPath.fillColor;
            paper.project.activeLayer.addChild(hole);
        });
        // ...