When --noImplicitAny is enabled, don't report errors suggesting that a 'void' function can be 'new'ed

[ghost]

Previously, on this code:

function f(this: void): number { return 0; }
new f();

With --noImplicitAny there were 3 errors: The first saying the return type should be void, the second saying it can't have a this type, and the third saying it must have a construct signature. The first and second errors are misleading because neither of those will fix the problem -- with --noImplicitAny void functions are not new-able.