if stdout is not a tty, replace clack.spinner by console.log

[Fil]

closes #1447
closes #1446

I'm not happy that I had to make c8 specifically ignore the non-coverage of the non-tty output tests, but I did not find a better way. (solved in the new approach, see below)

[mythmon]

Generally we've been pushing these tty checks higher in the call stack, so that we can have different messages on non-TTYs. In the deploy effects we have a isTty variable that we can use in tests to test both kinds of messages. I'd prefer if we keep that pattern instead of making Clack sometimes behave differently.

[Fil]

isTty tests whether stdin is a tty, which will orient the questions one way or the other.

This by contrast is checking if stdout is a tty, so that we know not to output control characters; this is similar to what we do with color() in

framework/src/tty.ts

Line 21 in f0e45f1

return process.stdout.isTTY ? (text: string) => `\x1b[${code}m${text}\x1b[${reset}m` : String;

(In a sense, isTty is poorly named.)

[mythmon]

I suppose we should add isStdinTty and isStdoutTty (I'd keep a isTty that is equal to isStdinTty && isStdoutTty too).

My point was more that we should push this up the stack, and leverage the effect system instead of doing it at import time.

[Fil]

@mythmon I've tried a different approach, hopefully closer to what you had in mind?

[mythmon]

I think that's better. Good enough to merge at least so our CI logs look better.