rq child process logging broke burst click logs and unit test cli ckan jobs worker --burst logging

[duttonw]

ckan (master) has moved from
rq==1.16.2
to
rq==2.3.3

There has been subtle changes under the hood where the worker thread is now spawned as a child and may not synchronise log back to click cli routing. This causes many tests looking for assert "Express Load completed" in stdout to fail even though the job passed on what occurred on inside ckan processing.

[ThrawnCA]

Since we have added the --sync flag to enable synchronous XLoader processing, we should be able to adapt our tests. We can split them to have one test that just confirms the queued job ran, then another that synchronously runs XLoader and verifies the right logs are output.

[ThrawnCA]

Encountering difficulties around changes made to the index_package function and how it interacts with custom package schemas.

[ThrawnCA]

It turns out that some corner-cutting for the sake of efficiency (skipping API layer to go straight to the model) in ckan/ckan#3245 interacts badly with recent changes made for ckan/ckan#8395

Apparently resource_patch is more efficient than it used to be, and so the API layer can now be used correctly.