A missing required module should not prevent starting of other modules

When a required module is not started for any module, all modules are not started, including the ones which have all their dependencies started. As a result, the end user does not even have a way of starting the required modules because the legacyui module is not started and yet it is the one with the page to help the end user start the required modules.
This should be fixed to the state we had before, where the module engine would still go ahead and start other modules which are fine.