`!.` after `?.` should be warned

This is an anti-pattern on the current type system. And the compiler must not do quick fix so. `!.` after `?.` is simply replaceable with `?.` and should do so. <!-- Please try to reproduce the issue with the latest published version. It may have already been fixed. For npm: `typescript@next` This is also the 'Nightly' version in the playground: http://www.typescriptlang.org/play/?ts=Nightly --> **TypeScript Version:** 3.7.x-dev.20191105 <!-- Search terms you tried before logging this (so others can find this issue more easily) --> **Search Terms:** **Code** ```ts document.querySelector('_')!.textContent!.split('') // old code document.querySelector('_')?.textContent!.split('') ?? 0 // string[] document.querySelector('_')?.textContent?.split('') ?? 0 // string[] | 0 ``` **Expected behavior:** ```ts document.querySelector('_')!.textContent!.split('') // old code document.querySelector('_')?.textContent!.split('') ?? 0 // unsafe, warning document.querySelector('_')?.textContent?.split('') ?? 0 // safe ``` **Actual behavior:** ```ts document.querySelector('_')!.textContent!.split('') // old code document.querySelector('_')?.textContent!.split('') ?? 0 // unsafe, no warning document.querySelector('_')?.textContent?.split('') ?? 0 // safe ``` **Playground Link:** <!-- A link to a TypeScript Playground "Share" link which demonstrates this behavior --> **Related Issues:** <!-- Did you find other bugs that looked similar? -->