Extending Tasks

Defining tasks solely in the Config file's `init()` method requires a single entry point for all scheduling. It might be good to offer a way to extend this to libraries and modules, so (for example) an Auth library could "register" its own tasks for periodic cleanup of spam accounts.

Start by reviewing how tasks are currently defined through the Config file's init() method and how scheduling consumes that single entry point. Define what an extension mechanism for libraries and modules would need to support, including an Auth library registering periodic cleanup tasks. Done means task registration is no longer limited to one central configuration entry point.

Written by the indexing model from the issue text.