Suggestion: Change config.toml spawn behavior.

[MarcG2]

DivaModManager will generate a new config.toml file if it detects a mod that doesn't already have one. The new file only contains the enabled parameter. So the mod isn't going to work as is . It'd be more helpful if it simply greyed out the mod and forced the user go find and copy the proper config file.

When users copy mods to the directory, there seems to be a chance the config won't properly copy over. It seems to happen somewhat often based on what I've seen in the Discord chats.
I'm not sure what causes it. But I speculate that DivaModManager auto reading the directories might somehow be causing the copy failure.