Improve inference for Promise.all of 'never[]'

[rbuckton]

This adds overloads to Promise.all to improve treat a Promise.all for an array of type never[] as a Promise<never> rather than a Promise<never[]>.

Fixes #37856

[andrewbranch]

Makes sense to me, but should we run user tests?

@typescript-bot user test this

[typescript-bot]

Heya @andrewbranch, I've started to run the parallelized community code test suite on this PR at eb27d3e. You can monitor the build here.

[typescript-bot]

The user suite test run you requested has finished and failed. I've opened a PR with the baseline diff from master.

[andrewbranch]

There’s one relevant change: https://github.com/typescript-bot/TypeScript/pull/54/files#diff-ce8b151b649148d02935b814380073d7

[rbuckton]

Yeah, looking at this a little bit more, there really isn't a way to craft the overload list to get the correct result here.

[rbuckton]

Actually, I may have found a solution. I'll try that first before giving up on this line of thought...

[rbuckton]

@typescript-bot test this
@typescript-bot user test this

[typescript-bot]

Heya @rbuckton, I've started to run the parallelized community code test suite on this PR at b486b5e. You can monitor the build here.

[typescript-bot]

Heya @rbuckton, I've started to run the extended test suite on this PR at b486b5e. You can monitor the build here.

[rbuckton]

Even this doesn't work because it collides with Promise.all<T> in vscode for cases like Promise.all<string[]>(...) when the intended return type is Promise<string[][]>.

For reference:
https://github.com/typescript-bot/TypeScript/pull/54/files#diff-0e62d568d28b82cee9e66b2b8fafd290R7

[rbuckton]

I'm switching this to a draft PR for the time being while I consider other alternatives.