Support for Vortex mod manager

[focustense]

Vortex has a staging directory that looks a lot like Mod Organizer's mod directory, although the subdirectories are named differently.

In particular, multiple files or versions from the same mod are not merged in Vortex, so you can end up with:

• ModName-{NexusID}-{VersionInfo}
• ModName-{NexusID}-{OtherVersionInfo}
• OptionalFileName-{NexusID}-{VersionInfo}

etc.

Thus it is possible, albeit quirky, to infer the concept of a "mod". We have to group by the Nexus ID and perhaps try to figure out the "primary" mod name in a context-dependent way, or perhaps some combination of heuristics such as total size (could be tricked by a 4K texture addon) or the presence of ESPs/BSAs (tricked by updates/patches) and other checks. Individually none of them are reliable, but put together, they might be useful. Alternatively, maybe there is some metadata in the file system that could tell us without having to use the Nexus API, or maybe there is some other Vortex file we could read to get that info. I'm not a Vortex user so I don't know offhand.

But there is probably some way to do this, quirky though it may be, and if so, then there is no reason why EasyNPC needs to be a Mod Organizer exclusive.

The final question is whether the generated mod directory will actually show up in Vortex. Possibly, it happens automatically or after a refresh/restart, as Vortex does support "offline" mods. Or possibly it has to be registered somehow and instructions need to be provided in the docs. Will require testing and/or input from Vortex users to figure out.

Ideally this would be made available with the first Nexus release, since Vortex is obviously prevalent there.

[focustense]

Tons of good progress here, and I'm almost ready to say that Vortex is fully supported. There are two small improvements that I think should go in before launch:

1. Pass the staging directory from Vortex on initial launch, when using the extension.

   For users who read the documentation - which will need to be updated - and install/use the extension before running EasyNPC for the first time, it just makes sense to save them the effort. We know what the staging directory is already. Also, there may be some users who discover EasyNPC from the extension, and again, we can save them a step.

2. Show the Vortex warning/extension link when the mod root directory is changed to a Vortex staging directory.

   This is really about making sure all the bases are covered. If some users decide to skip steps or follow a weird or unexpected process to get themselves set up, it's a good idea to make sure they don't get lost in the shuffle.

The first one is important, in my opinion. The second can maybe wait a bit, as I don't expect a ton of users to actually do that, or switch to Vortex from Mod Organizer, etc. And if part 1 is implemented, then part 2 becomes unnecessary 99% of the time.