Q definitions compile with --noImplicitAny without warnings.

Some types gained explicit any, others what looked to be the correct type (void, some function, promise, etc.). Only tested on a codebase that uses a few Q functions, but I'm assuming the compiler gets this right anyway.