Normal output to stdout, error & diagnostic output to stderr

[robsheldon]

I have mkcert integrated into some automated process that do setup/teardown. A typical pattern for utilities invoked by these processes is foo >/dev/null || error... or if ! foo >/dev/null; then....

In these cases, normal program output is suppressed, but if the program encounters an error, they probably write something to stderr and that gets collected in the overall process log and can be helpful for debugging.

By default, the log package used by mkcert sends all output to stderr, so now the pattern is mkcert 2>/dev/null or mkcert >/dev/null 2>&1.

This might be related to #196. I get the reasoning for not adding a -q or --silent option, but without that, and with all output (ordinary or otherwise) sent to stderr, my choices are Created a new local CA 💥 etc. etc. in my logs, or no output at all in the event that something goes wrong.