[2.0.76] Updating a disabled mod enables new dependencies, ignoring the mod is disabled

[protocol_1903]

As in title. This only happens with the 'Automatically enable new mods' setting on.

Reproduction steps:

1. Install Powerless v0.1.4 manually to the mods folder, either from the mod portal download or attached here.
2. Open the game, and ensure that the mod is disabled. Restart to disable it if need be.
3. Update Powerless to 1.0.2. Observe that Burner Beacons, Nonstandard Beacons, and PEREL are installed as well.
4. Navigate to the manage menu and observe that the newly installed mods have been enabled even though the dependent mod is disabled.

If repeated with 'Automatically enable new mods' disabled, the mod will be installed but left off. While this logic is technically truthful to the setting name, it's a bit antithetical since the dependent is disabled and the mod was not manually installed by the player and the player has no knowledge of it being enabled. In the pY server, we've have had multiple people loose tens of hours of progress because another installed but disabled mod was updated with a new dependency, the dependency was enabled without notifying the player, and their bases were promptly broken without being noticed because of the changes of the new mod. I propose that when installing new dependents, the setting is ignored entirely, and the mods are only enabled if the dependent is enabled. This would warrant a tooltip on the mod setting but I believe it would cause fewer issues than it would solve.

[Loewchen]

95694