Gracefully handle global promise pollution

[lorefnon]

• Update QueryInterface to proxy to only standard promise methods
• Update QueryInterface type to be explicit about the methods being
  proxied

This primarily handles pollution of global Promise (either the type or
the global object at runtime) by other libraries.

Fixes: #3422 (comment)

[onehorsetown]

e9fd66e

This change broke TSLint for my TypeScript project. Everything lints fine in 0.20.0, but with 0.20.1, I get tons of:

ERROR: (await-promise) ... Invalid 'await' of a non-Promise value.
ERROR: (no-invalid-await)  ...Refactor this redundant 'await' on a non-promise.

Trying to figure out why the tslint no-invalid-await and await-promise don't think this is a promise/thenable/etc.

[lorefnon]

Do you have "await-promise": [true, "Thenable"] in your tslint config ?

[onehorsetown]

@lorefnon Yes, I've tried every variant of

"await-promise": [true, "Thenable", "PromiseLike", "Bluebird", etc...]

I've stopped in the TSLint code and the name of the type at the point where it is checked is __type. So, this actually makes the problem go away, but seems very wrong:

"await-promise": [true, "__type"]

The other linting error (no-invalid-await) is coming from the tslint-sonarts package which is checking if the type has a then method right here:

https://github.com/SonarSource/SonarTS/blob/4a4080b78001a78d758d1d0fa0190fb9496b6f57/sonarts-core/src/rules/noInvalidAwaitRule.ts#L57

At that point in the linting code, the ChainableInterface does not have a then method, but I have no idea why.

[72636c]

You can make an exception with "await-promise": [true, "ChainableInterface"]

[onehorsetown]

You can make an exception with "await-promise": [true, "ChainableInterface"]

@72636c - That fixes it. Thanks.

The other issue I then have is that the tslint-sonarts linting plugin does not think the Picked type does not have a then method... which it, of course, does.