Add environment variable check to force console output

[timwoj]

Taken from @awelzel's suggestion in #143 (comment).

Fixes #143

[bbannier]

WDYT about adding a proper option for this, and also reading a default from the environment like we do for --progress-bar?

btest/btest

Lines 3026 to 3033 in 1e97bbe

	optparser.add_option(
	"-P",
	"--progress-bar",
	action="store_true",
	dest="osc94_progress",
	default=os.environ.get("BTEST_OSC94_PROGRESS", ""),
	help="display progress bar using OSC 9;4 escape sequences (set BTEST_OSC94_PROGRESS to permanently enable)",
	)

It would also be nice to add a test for this.

[ckreibich]

I agree — my suggestion would be to expand this PR a little bit. How about:

• add --tty to force console use
• use BTEST_FORCE_TTY as the corresponding variable
• wrap sys.stdout.isatty() or os.getenv("BTEST_FORCE_TTY") into a helper and use that instead of sys.stdout.isatty(). We have multiple of these and I'm not sure e.g. --progress works reliably in that Windows setting either.

If you have it in you it would also be handy to get a summary of supported BTEST_* env vars in the help output. I just had to remind myself and there are more than I would have come up with. :-)