[BUG] Remove CRT dependency on Windows build

[alexchandel]

Checks

• I have read the troubleshooting section and still think this is a bug.

Describe the bug you encountered:

The inspiring project rg has no dependencies on any of Microsoft's obnoxious redistributable components, even in its MSVC release:

However fd's Windows release still depends on the VC v14 redists:

This means fd errors at launch on machines without this redist installed (and sadly, there are many, many of these still in the wild in industry). But this DLL dependency is not necessary and unhelpful on balance. The only functions used are the basic mem functions:

and some low-level CRT functions unrelated to fd's core functionality that can be statically linked with no consequence, e.g.:

Describe what you expected to happen:

fd should statically link the UCRT for better performance and portability.

What version of fd are you using?

fd 10.3.0

Which operating system / distribution are you on?

Windows 11 (and several other older Windows)

[tmccombs]

I don't know enough about building on windows to know how to fix this.

[b4shful]

@tmccombs Found the relevant PR for ripgrep which does exactly this, no more, no less.
Check out BurntSushi/ripgrep#1613

Seems like statically linking the C runtime when building on MSVC can be achieved simply by adding a .cargo/config.toml file containing:

[target.x86_64-pc-windows-msvc]
rustflags = ["-C", "target-feature=+crt-static"]
[target.i686-pc-windows-msvc]
rustflags = ["-C", "target-feature=+crt-static"]

ripgrep also does the same for MUSL targets, see https://github.com/BurntSushi/ripgrep/blob/master/.cargo/config.toml