Make DisableModModal more self-sustained

[anttimaki]

No description provided.

[anttimaki]

Changes in this PR allows running "disable BepInEx and all dependants" on a profile with 282 mods in under 20 seconds, whereas before the changes it took 40+ seconds.

While the changes in this particular PR doesn't seem to affect the speed of the first local mod list rendering, it's worth noting the effect this four PR stack has on that performance (numbers with same 282 mod profile and dev build):

• develop branch: ~16 seconds
• update-all-query-performance on top of develop branch: ~9 seconds
• This branch on top of develop branch: ~20 seconds
• update-all-query-performance on top of this branch on top of develop branch: ~13 seconds

In other words the changes in this stack seems to eat roughly half of the gains from update-all-query-performance. On the other hand the changes do speed different use cases after the list have been rendered significantly, and at least IMO cleans up the code quite nicely.

Anyway the question remains, are these changes something we're willing to merge? I don't think makes much sense for me to build on top of this stack before I have the answer to that. I'll try to see if I can improve the performance without messing with the same files, and if not, then do something unrelated to performance instead.

[anttimaki]

Based on Discord discussion, changed the PR so that mod disabling is done via Vuex. Initial rendering of a profile with 282 mods now takes ~3 seconds, thanks to other changes that have been merged since the PR was first opened.

[MythicManiac]

Spotted a couple of potential improvement areas within the context of this PR directly, but nothing I'd consider a blocker myself.