Ease of debugging/understanding the python configuration

make_velout_tracks is just another name for the cpp algorithm name VeloUTTracking (adding only default hits). It is not at all clear if we want to "normalize" the name in this manner or just have a naming convention which keeps the original cpp name, like make_VeloUTTracking_output or variations of this. The obvious drawbacks of normalizing is that people have to come up with new names and you cannot easily "skip" this level of abstraction when drilling down.

Easier debugging may also be achievable in a different way, in which case this can be closed.

Started from this discussion