bevy_log: Support Windows CMD formatting

[griffi-gh]

What problem does this solve or what need does it fill?

ANSI Escape sequences make logs unreadable in cmd

What solution would you like?

Either disable ASII escape codes for cmd or use the Windows CMD-specific ones

What alternative(s) have you considered?

N/A

Additional context

[djeedai]

This boils down to detecting whether the current environment is a terminal (TTY) that supports ANSI codes, which probably requires a helper dependency crate to do that for us.

I did some quick research:

• crates like atty or crossterm return true when querying "is a TTY?" while running in any Windows terminal I tried (CMD.exe, Terminal, VSCode embedded term), so don't give the right info (admittedly, because this is the wrong question; but mentioning anyway for completeness).
• crates like ansi_term allow manipulating colors, but already assume that ANSI codes are supported, so are of no use (mentioning because ansi_term is quite popular).
• the solution seems something like the enable-ansi-support crate, which tries to enable ANSI code support on Windows (this is no-op on other platforms since they all support it), and returns an error code if it fails; this gives us 2 nice things:
  1. we know if we're on an older Windows terminal and need to disable ANSI codes (and in particular colors)
  2. if on a Windows 10 terminal, the call enables support for colors, so brings the Windows experience on par with other platforms as an added bonus