Feature #8434: Get rid of job classes
Always start up the same Core components
A long ago I assumed that we will have a lot of job classes for various types of target programs, and for each such class it will be necessary to specify a corresponding component chain. Now I think that it would be better to always start up the same Core components while specify target program types in a job configuration. Core components will find appropriate plugins. That was already done for generation of verification and verification tasks. So, now this should be implemented for high-level components as well.