Statically link C-runtime for MSVC Windows

[ducaale]

On windows, xh requires VS C++ Runtime Redistributable to be installed or will fail with The code execution cannot proceed because VCRUNTIME140.dll was not found. This PR changes that by statically linking the C-runtime.

Also, see BurntSushi/ripgrep#1613

Partially resolves #219

[blyxxyz]

Hm, is this really something we want to specify for the whole project? Maybe it should be limited to the release action.

[ducaale]

The other option would be to use the RUSTFLAGS environment variable. I will see how I can do that in .github/workflows/release.yaml.

[ducaale]

Should I set RUSTFLAGS in other places as well?

[blyxxyz]

Can you run the release action somewhere for a binary we can test with?

[ducaale]

Sure, I have created https://github.com/ducaale/xh-temp-111 for testing purposes. I'll grant you push access in a moment.

[ducaale]

Unless I set shell to bash, RUSTFLAGS will not get passed to cargo in the next step.

[blyxxyz]

Should we perhaps also move LTO from Cargo.toml to the release CI? An incremental rebuild takes 10s without it and 1m30s with, that's annoying when benchmarking.

[ducaale]

I will need to add Cross.toml file so cross can be configured to pass RUSTFLAGS to the underlying build environment.

Edit: I am currently experimenting with CARGO_PROFILE_RELEASE because enabling lto via RUSTFLAGS errors

$ RUSTFLAGS="-C lto" cargo build --release
   Compiling autocfg v1.0.1
   Compiling libc v0.2.101
   Compiling version_check v0.9.3
   Compiling proc-macro2 v1.0.29
error: options `-C embed-bitcode=no` and `-C lto` are incompatible

[blyxxyz]

Looks good! Unlike v0.14.1 it just works on a clean Windows installation.