megathread: Known sudo issues in Windows insider builds

This is a megathread for all the issues that we had previously identified before sudo was made public. There's about a 3-week delay between us fixing issues, and the fixes being available to Insiders. This creates a bit of a backlog of issues that we've already fixed, but that are still present in the Insider builds.

### Bugs fixed by 1.0.0-38, !10359415
- [x] Sudo server listens for a single connection
- [x] `sudo -N` always starts Windows applications in C:\windows\system32 - this is by design, but mitigated with:
- [x] #22 
- [x] Sudo events weren't showing up in Event Viewer
- [x] Regression from `26068`: `sudo pwsh` reports an error about "Processing -File '' failed: The path is empty"
- [x] Sudo with an explicit mode will report an error instead of clamping to the available mode

In ge_release_we_adept_dev on 2/28. ETA ~3/20?

### Bugs fixed by 1.0.0
- [x] `sudo` seemingly doesn't return the exit code of the target application??
- [x] Localization is quite a bit better
- [x] Sudo does a _better_ job of checking that the client process is sudo
- [x] The elevated sudo exits immediately after launching the target process
- [x] #21 
- [x] `--newWindow` was replaced with `--new-window` (!10282477)
- [x] Added `-N` for `--new-window` (!10282477)
- [x] `--disableInput` was replaced with `--disable-input` (!10282477)

Apparently this one is in ge_release 26068, 2/25

### Bugs fixed by 0.1.6
- [x] Localization is largely not available
- [x] Sudo doesn't log requests to the Event Viewer
- [x] `sudo dir` from powershell will do the `cmd` `dir`, not the powershell `dir`
- [x] `sudo -E --newWindow cmd` doesn't actually pass env vars to the target process
- [x] eleveated sudo doesn't check that the client process is sudo (MSFT:48520593, fixed in !10167063)

0.1.6 merged to OS.2020 in !10239101. It's in ge_release_we_adept as of 2/14, and ge_release as of 2/25, build 26068

### Bugs fixed by 0.1.5 (Windows Insiders build 26052)
- [x] The sudo icon is out of date
- [x] MSFT:48453238 Piping to files is broken

Start by reading the tasklists in issue #4 and the referenced release/build notes. No source files or tests are named, and every listed bug is marked fixed, so the issue does not define an actionable change or a clear done condition for a new contributor.