yes: handled stdout being closed (EBADF)

[jstarkman]

Now, both exit 1:

$ yes >&-
yes: standard output: Bad file descriptor

$ ./target/debug/yes >&-
yes: standard output: Bad file descriptor (os error 9)

closes #11090 (infinitely writing its buffer to /dev/null on FD 1)

[github-actions]

GNU testsuite comparison:

Note: The gnu test tests/rm/many-dir-entries-vs-OOM is now being skipped but was previously passing.
Congrats! The gnu test tests/csplit/csplit-heap is now passing!
Congrats! The gnu test tests/printf/printf-surprise is now passing!
Congrats! The gnu test tests/tail/tail-n0f is now passing!

[xtqqczze]

Do we need to set exit code?

[jstarkman]

Do we need to set exit code?

Handled by the caller:

        Err(err) => Err(USimpleError::new(
            1, // code

This matches GNU's exit code:

$ yes >&- ; echo $?
yes: standard output: Bad file descriptor
1

$ ./target/debug/coreutils yes >&- ; echo $?
yes: standard output: Bad file descriptor (os error 9)
1