Mark virtual dependencies as auto-installed

[HebaruSan]

Problem / Motivation

1. Install a mod with a virtual dependency (i.e., one in which the user is asked to choose which module to use to satisfy it)
2. Pick whatever when prompted
3. Finish installing
4. The dependency is not marked as auto-installed, even though it is only there because another mod needed it and would probably make sense to remove if the user removes the depending mod

Cause

Virtual dependency choice is driven by a TooManyModsProvideKraken exception that halts the install. Then the UI prompts the user to choose, adds their choice to the changeset, and re-starts the install. So virtual dependencies are always in the changeset, making them appear as manual user choices. (xref #2753)

Changes

Now when the user chooses a mod to satisfy a virtual dependency, each UI adds the module to a list of mods that should be marked as auto-installed, which is passed to InstallList and Upgrade and used to set the autoInstalled parameter of Registry.RegisterModule.

Fixes #4428.

Caveats / Objections

I don't love adding a new parameter to InstallList and Upgrade for this, or making this common requirement live in UI-specific code. I anticipate a future project to:

• Remove InstallList, Upgrade, and UninstallList from ModuleInstaller
• Eliminate TooManyModsProvideKraken
• Add a ModChange object to Core
• Add an ApplyChanges to ModuleInstaller that:
  • has a parameter for a read only collection of ModChanges
  • has a parameter for a callback to choose a module to satisfy a virtual dependency
  • has its own list of auto-installed modules to which it adds such virtual dependencies

This would dramatically simplify the per-UI code for installing by better encapsulating the common/redundant logic in one place in Core.

... but that's a pretty big change, and for now this way of doing it is pretty minimal and safe and will serve as an anchor to ensure this feature is incorporated into that future rewrite, should it occur.