Prototype of new architecture, without work manager API.

[rtibbles]

Starts the server inside the application process.
Defers only task workers to a foregrounded service.

[dylanmccall]

This will fail awkwardly if we're using Kolibri < 0.16. Should we add an extra check to the Makefile so this gets caught early?

[rtibbles]

Can do - we've mostly relied on tagging and versioning of the installer repos to keep that in check, but doesn't hurt to add extra.

At the very least, we can update the README.

[dylanmccall]

This looks pretty good to me and I have a branch merging it with some of the stuff we've glued together downstream: endlessm#20. I also add a bit of refactoring, and my thought is I'll split that into a different pull request once we have this sorted out.

Using the newest build of Kolibri from the develop branch, the workers service seems to be doing its thing: worker-related stuff appears in logcat without any obvious errors. With that said, it does run into an error importing content, but I think that's just a problem in Kolibri, not here. (It gets a 404 requesting /device/api/device_channel/000409f81dbe5d1ba67101cb9fed4530/?include_fields=total_resources%2Ctotal_file_size%2Con_device_resources%2Con_device_file_size%2Cnew_resource_count%2Cnew_resource_total_size&1652997798744=1652997798744, and then throws an exception here: https://github.com/learningequality/kolibri/blob/1fd1fc08c92eae64634126a757c9e1af442870c2/kolibri/core/assets/src/api-resources/task.js#L14-L16).

[rtibbles]

Oh yes, absolute latest develop is completely broken on the frontend for tasks - because of some of the Task API refactoring that I alluded to earlier. I am fixing it as we speak.

[rtibbles]

Going to merge this for now, we can make more updates as we go.