Parallel template-execution: marking console logs by thread/template

[colleenXu]

Maybe for next phase.

With parallel template-execution, it's harder to understand the console logs (what template they're associated with). I've discussed this with Jackson.

It would be nice if each console log was marked with what template it was executing (can be the order in the templateGroup list).
Or if the console logs for each template-execution was marked with an ID, and some console logs at the beginning mapped each ID to what template was being executed.

Err...but this may be complicated to do, particularly since this (1 creative query's execution) all happens in 1 thread. And the template-execution-level logging is separate from the module keeping track of what info goes with what template.

[rjawesome]

PRs use Node.JS Async Hooks to annotate debug logs with the appropriate template name when running in creative mode. Ex below:

The major changes are in utils (which contains most of the new debugging code) and query graph handler (which adds the context of the template to each promise).