Blocking behaviour on status check invoke

Tobbs spotted that the initialisation logic that runs the status check on the projects will block until everything is complete despite the use of a goroutine and a channel, implement his suggestion to wrap the whole thing in what I'm assuming is another goroutine.

If it's not fast why bother right?

Start by locating the initialization logic that invokes the project status checks, then trace how its goroutine and channel interactions cause the call to block. The work is done when invoking the status check returns without waiting for every check to complete, with the relevant behavior verified by the project’s available checks.

Written by the indexing model from the issue text.