Fix invisible file path text in PowerShell

[latkin]

Fix for #342

Root cause is that the standard Windows PowerShell launch shortcut sets the console background color to "dark magenta", then re-defines "dark magenta" as RGB(1, 36, 86) aka "powershell noble blue." Thus if a console app writes output with "dark magenta" foreground color, it will be invisible in a default PowerShell console.

Fix is to do a simple, Windows-only check for a "dark magenta" background at startup, and in this case change path output style to "intense magenta," which will render fine.

Result:

Potential concerns:

• Arg parsing now has to know about Windows console. That's not great but it was simplest path forward for me as a rust n00b.
• This will add "intense" styling to path output even when user has manually overridden the color themselves. Additional path:style:nointense will be needed to counteract this change.
  • Seems not terribly burdensome. By definition this will only affect users who are already comfortable overriding color settings.

[BurntSushi]

@latkin Thanks for doing this!

I'm not sure if this is the path I necessarily want to go down. In particular, what do you think about just changing the default colors on Windows and removing the conditional check altogether? That way, we don't interfere with any specific user settings but we avoid the "text is invisible" problem by default.

Tangentially, I did a lot of work to avoid making wincolor a direct dependency on ripgrep in an effort to hide that layer of abstraction. I'll bow to the alter of pragmatism if necessary, but I think I'd rather see if we can get away with just changing the defaults for now.

[BurntSushi]

I'd rather not rename these methods, since that would be a breaking change.

[latkin]

@BurntSushi No problem, I understand your concerns. If you are ok with simply changing the Windows defaults, then that's even easier :-) I went with Cyan for now.

PR udpated. New behavior:

[BurntSushi]

Fantastic, thank you!