Deleting files outside the App results in impossible to deploy files

[Al12rs]

Outline:

Deleting files outside the app results in irreversible ban of the file from deployment.
Only solution is to abandon loadout and restart from scratch.

Problem:

If you delete a file outside the app, the deletion gets picked up by the app and placed in the hidden Overrides mod.

That deletion entry will from then on prevent any file with the same destination from being deployed.
The deletion entry itself can't be removed, cleared, or in any way be interacted with. It is also in no way visible to the users.

The only way a user has to allow the app to deploy files to that destination again is by starting from scratch, abandoning their loadout with all their mods.

This experience is horrible for users, that don't know why some files are not getting deployed. It is also horrible for giving support as users will rarely be able to tell whether they have deleted some file at some point or not.

Steps:

To reproduce:

• Install a BG3 mod with a pak file
• Delete the BG3 pak file from BG3 %localappdata%\Larian Studios\Baldur's Gate 3\Mods.
• Attempt to install the same pak file from the app again
• pak file will not be deployed
• pak file is now cursed

[LukeNexusMods]

Steps for solution:

• When there is an outside deletion, we add a reified delete to Overrides mod.
• If the reified delete already exists, we do nothing. Currently we add a second delete which is a problem.
• If an outside file addition appears that was previously deleted, we remove the reified delete from Overrides, and add the file to overrides if it differs from the winning mod. (Or let game specific code decide where to put it, e.g. SDV config files).

The above does not help if the user is attempting to add the file back from within the app.
To solve that, users need the ability to edit the contents of Override.

• File Manager  #2330