[expo-cli]<feat>: Add cmd.exe detection on windows & warn about it

[bbarthec]

Resolves #2107

I've only succeeded in checking whether the expo-cli is run from cmd.exe.

HOW

I've found a package that seems to be quite popular and behaves similar to ps aux: https://www.npmjs.com/package/ps-list.
I'm using it to find the parent process of the current running program taking advantage of NodeJS API process.ppid.

The problem with this approach is that on Windows we're querying the processes table and that is taking some time.
I've measured the timings on VMWare Fusion running Windows 10 and checking for cmd.exe takes ~200ms.

PREVIEW

ABOUT WSL

Unfortunately, I've failed to find any reliable way to distinguish between WSL v1 & v2.
There's a package that can detect running the script on WSL though (https://www.npmjs.com/package/is-wsl), but once we're in WSL we don't really need to warn about it 😅

Although there's a way to check WSL version:

PS C:\Users\Bartłomiej Bukowski> wsl -l -v
  NAME            STATE           VERSION
* Ubuntu-20.04    Running         1 <<- this is version

it only runs in PowerShell/CMD, so we're unable to check from inside WSL what version we're running using this technique.

[brentvatne]

The problem with this approach is that on Windows we're querying the processes table and that is taking some time.
I've measured the timings on VMWare Fusion running Windows 10 and checking for cmd.exe takes ~200ms.

ah, that's too bad. some ideas:

• maybe we can make this an asynchronous warning rather than blocking
• we could cache it per pid so it's only slow the first time you run it in a terminal (seems like a lot of work for a small feature like this)
• we could move it to expo doctor or expo diagnostics

[bbarthec]

@brentvatne, I've adjusted the warning, detection process (removed the ps-list dependency, bc it is shipped with fastlist binary for windows) and scoped the detection into doctor command.