[1.1] Bug: when tasks are nested, newly registered autoloading path does not take precedence over older ones if it was already registered before.
Bug example: registering /a/, then /b/, then /a/ again will give autoloading precedence to /b/, so if a task needs /a/ then /b/ and another needs /b/ then /a/, the first to do it will forbid the other one to bahve correct.
This allows tasks to override their parent task autoloading settings and thus showing correct behavior when an application overrides a plugin's model task (otherwise, the load-data part in build-all-load doesnot behave the same way on its own and within the combo task)