Improve start-up time from using jurigged

[JamesHutchison]

The jurigged library creates start-up and import overhead. As an example, if it took 50 seconds before, it may take a 1:20 now to run a test for the first time. This creates a compromise and can add to developer consternation if they are forced to reload the server frequently. It's unlikely a developer needs to run a test for the first time, and then immediately run it again, so there may be an opportunity to run the jurigged work in the background, hiding the overhead from the dev.

[JamesHutchison]

The codefind library is a potential culprit, specifically codefind.registry.CodeRegistry.collect_all, however its unclear how much can be saved since a bulk of the cost is in I/O calls

[JamesHutchison]

Possibly related: breuleux/jurigged#31