feat(categories): debounce writes, repair from AutoTMM code.

[KyleSanderson]

Repairs from AutoTMM torrents when categories are corrupt. Please feel free to edit / commit to / and or create another PR based on this.

[KyleSanderson]

This should be ready again, I believe I have bikeshedded this to death.

[KyleSanderson]

@glassez this isn't a 5.1 problem like I first thought it was, I just had this corruption happen again on 5.0. Is there anything else I can do with this PR to get this corruption issue resolved.

[glassez]

@KyleSanderson
Could you describe the problem and how do you solve it in this PR? I would like to understand your intentions before I can review the code.

[KyleSanderson]

@KyleSanderson Could you describe the problem and how do you solve it in this PR? I would like to understand your intentions before I can review the code.

categories.json is written to entirely every single category change, there is no locking on this from what I could see. Additionally, when categories.json is corrupt, restore the save_path from the torrent information, if such data still exists. Right now it just recreates the categories, moving thousands of torrents to the category name as opposed to the save_path that was there.

[glassez]

@KyleSanderson
They look like two different issues:

1. categories.json is written to entirely every single category change
2. when categories.json is corrupt, restore the save_path from the torrent information, if such data still exists

So I believe this PR should be decoupled into two ones in order to improve their further reviewing and understanding.

[github-actions]

This PR is stale because it has been 60 days with no activity. This PR will be automatically closed within 7 days if there is no further activity.

[KyleSanderson]

Still fixes the rampant corruption the category race condition code has.

[glassez]

Still fixes the rampant corruption the category race condition code has.

So would you mind to decouple it into two PRs in order to improve their further reviewing and understanding as was suggested above?

[github-actions]

This PR is stale because it has been 60 days with no activity. This PR will be automatically closed within 7 days if there is no further activity.

[KyleSanderson]

.