Experimental fix for [issue 2312]

[JustSimplyKyle]

This pr is an experimental fix for #2312
it doesn't change the underlying logic, just the events that's tracked.
(this is just me adding random events to the track list until it fixes the hot-reload issue)
This works under helix and vscode, not sure if neovim has the same behaviour
@Andrew15-5 mind testing?

[Andrew15-5]

If we have an image or something called img.png and then we want to rename it. If the file name is changed to image.png first in the Rust code, then the dx will show the unknown file error. After renaming the file (mv img.png image.png) the watcher won't see it and the workflow will be broken. Maybe re-saving the Rust file will fix this.

This is just an example that I come up with on the spot. This means that the potential FS manipulations can degrade the DX for everyone just so that you can use the default saving behavior in Neovim. I don't think this is worth it, if what I describe above is true. I don't really even know why other watchers (although I haven't used much of them, or I just can't remember them) don't complain about the Neovim's backup saving shenanigans. I only faced this problem with Rust/notify-based watchers (Dioxus/Typst CLI).

I can test this later (in a few days?), now I'm mostly busy.

[jkelleyrtp]

In our recent CLI overhaul I incorporated your changes into our watcher - will test against the original issue.

Thanks!

I'll make sure to adjust the commit to have your name on it for the release notes / contributor graph :)

[Andrew15-5]

#2312 (comment)

So, for that commit this isn't even necessary.