Prompt to also enable dependencies

[dineshm72]

When first launching FTC, you are able to enable some modules to start with. If these modules have dependencies, however, when the game first reloads you can find that the modules you were trying to start by default don't actually start, so you have to abort the process, reload everything, then try again.

Instead, it would be handy if FTC would prompt you to enable all dependency modules when you select a module to enable. (Maybe even always do it by default rather than prompting, though perhaps there might be a reason you want to test to see if an issue can be caused by a soft dependency, like libWrapper, which also has a fallback shim that might be usable by the original module you're enabling.)

Similarly, as the list of modules is automatically enabled and disabled in the background while the FTC process is going, it may be that some modules are enabled but their dependencies are not, which causes them not to load, or not to function. This could interfere with the testing process and give you a false negative that gets you into the wrong branch of the test. Fixing this could be very difficult, though, since some libraries might be dependencies of many other modules, so it might be very hard to figure out when and how they need to be enabled and disabled during the testing branching.

[franckflo]

I second that, it would be most useful. More and more modules use dependencies now.