`terminal_size::terminal_size()` is used to determine if stdout is
connected to a real tty/pty. In previous version of `terminal-size`,
this method only queries the terminal size for `stdout`.
However, it is changed in the following commit
eminence/terminal-size@08f0e73
Now the method will use `stdout, stdin, stderr`, trying its best to
determine the terminal size. This cannot be used to determine if `eza`
output is piped or redirected.
We should use `terminal_size_using_fd` on `stdout.as_raw_fd` instead.

Resolves eza-community#434 Fixes eza-community#433

The previous commit 427f975 uses
`terminal_size::terminal_size_using_fd` and `io::stdout().as_raw_fd()`
which are only available on unix platform, creating compatibility issue
for windows.
In this commit, I leverage rust conditional compilation and
`terminal_size::terminal_size_using_handle` to implement the same
functionality for windows platform.

We use functions in this crate to get stdout handler for
terminal size query.

Previsouly we tried to use `terminal_size_using_fd` on unix, and `terminal_size_using_handle` on windows to detect if stdout is connected to a terminal.
This can be done by using `std::io::IsTerminal` on `std::io::stdout`, eliminating the need of conditional compiling.

Another API misuse. `terminal_size::terminal_size()` now looks into `stdout`, `stderr` and `stdin` to determine the terminal size with best effort.
This is desirable for TUI applications, but not for CLI applications.
`eza` only cares about the size of the terminal which is connected to standard output.
We change this to `terminal_size_with_fd(stdout.as_raw_fd)` on unix, and `terminal_size_with_handle(STD_OUTPUT_HANDLE)` on windows.

`eza` manpage and `README` have been refering to this option as `--colo[u]r`. We should follow the tradition and keep the writing style consistent.

Co-authored-by: MartinFillon <[email protected]>
Signed-off-by: hehelego <[email protected]>