Paralives - Content Mod support

[vertigomaster]

Objective

• Creation of Paralives MO2 instances
• Game boots from MO2
• VFS points to Paralives local mod folder
• Can add and correctly map content mods (.mod folders)
• Content mods in instance work when Paralives is booted from the instance
• MySavedGames.mod directory is correctly handled (currently being incorrectly treated as an Override)
• MyOptions.mod directory is correctly handled (currently being incorrectly treated as an Override)
• The vanilla MyPremadeXX.mod directories are handled correctly
• Interfaces with Nexus Mods (downloads correctly, archives handled, categories import)

Known Issues

• Steam overlay does not appear
  • Steam workshop mods still appear to work correctly though
• Mod formatting not yet checked/sanitized with globs; most mod structures work fine, but some may need to be adjusted after/during mod install

Challenges

Paralives has a neat yet curious structure, where any and every change to the base engine is treated as a "mod", including game options ("modding" default settings to other values), save games ("modding" the default town state, adding Paras, lots, etc). As a result, the game places them in the same folder as other "traditional" mods.

The VFS seemingly needs to be adapted to either exclude these subfolders from the VFS entirely, or to at least correctly exclude changes to them from falling into Overrides so that non-mod data persists correctly.

Upcoming Plans

After this PR, the next target is implementing support for BepInEx, which appears to be the current solution for implementing script mods in Paralives.

Those mods live in an entirely different root (under the game directory, whereas the local mods folder lives under %LocalAppData%Low/Paralives/Paralives