ENG-148 Undefined behaviour when piping

Minor logic bug. It's fixed now. Prepping for merge.

This is the simplest and best solution I can think of right now. The core of the problem is that the process.stdin functions differently when piping into the node program. In such a way that prompts doesn't handle it properly.

Prompts fails to process this in two ways

1. A prompt takes a line as an input, but with the pipe wit will take the full stream as the first line. So if we piped password\npassword, it gets passwordpassword in the first prompt.
2. It can't handle the end of stream properly. So once the pipe has fully dumped it's data it keeps waiting for input. Resulting in a promise deadlock.

Initially I tried to solve this by creating a promise to track the end of the stdin stream. I could race the prompt with this to prevent the deadlock. but this results with a leaked prompts promise. Also the input from this isn't usable anyway.

The simplest solution is to not prompt at all when handling a pipe. The pipe still works, we just can't function interactively while doing it.

I looked into using the ttys library https://github.com/TooTallNate/ttys/blob/master/index.js. With this we can have the pipe but also the prompt still functions interactively. The library is simple so we can inline the code. However I'm not sure if it's very portable since it's trying to open a /dev/tty with fs.openSync('/dev/tty', 'r').

The only other solution I can think of right now is to detect the piping and have our own stream processor to extract the provided password. Similar to https://stackoverflow.com/questions/59308117/how-to-differentiate-between-standard-inputs-via-pipe-and-via-prompt-in-nodejs

I'm putting this on hold for now pending some discussion.

Did you synthesize the solution from https://www.npmjs.com/package/ttys?

We're going to go with the current behaviour I've implemented. Where we handle the pipe as if the user cancelled the password prompt.

I had to remove the tests using nExpect to check for prompting. It seems to be using a pipe to function so it's incompatible with the fix.

Ready to merge.