Disabling a module should automatically disable classes below it
In Foreman, we have a growing number of classes which can be enabled/disabled as "modules" in kafo, e.g.
I'd like kafo to treat --no-enable-foreman as implicitly also doing --no-enable-foreman-cli --no-enable-foreman-plugin-setup, and similarly --no-enable-foreman-cli would imply --no-enable-foreman-cli-bootdisk. This would make it easier for people to disable entire modules, and I think a little more intuitive. When users try to disable the foreman module and enable only foreman_proxy, they currently end up with loads of --no-enable arguments.
--enable options passed as well as a --no-enable should either override it (re-enabling a more specific module) either by ordering in command line arguments or based on specificity.