Cargo binstall falls back to cargo quickinstall for x86_64-pc-windows-msvc

[somehowchris]

Hey 😄

So as I have dug though cargo-bins/cargo-binstall#130 I used cargo-watch as an example.

It seems to me that although you are publishing zip files for windows, your binstall metadata doesn't point to it, so it falls back to cargo-quickinstall.

Sry, didn't have yet a chance to checkout your config of cd, but wanted to let you know 🦄

Some logs:

cargo run -- cargo-watch --no-confirm
    Finished dev [unoptimized + debuginfo] target(s) in 8.23s
     Running `target\debug\cargo-binstall.exe cargo-watch --no-confirm`
11:00:20 [INFO] Installing package: 'cargo-watch'
11:00:23 [INFO] Checking for package at: 'https://github.com/watchexec/cargo-watch/releases/download/v8.1.1/cargo-watch-v8.1.1-x86_64-pc-windows-msvc.tar.xz'
11:00:23 [INFO] Sending installation report to quickinstall (anonymous)
11:00:25 [INFO] Checking for package at: 'https://github.com/alsuren/cargo-quickinstall/releases/download/cargo-watch-8.1.1-x86_64-pc-windows-msvc/cargo-watch-8.1.1-x86_64-pc-windows-msvc.tar.gz'
11:00:26 [WARN] The package will be downloaded from third-party source QuickInstall
11:00:26 [INFO] Downloading package from: 'https://github.com/alsuren/cargo-quickinstall/releases/download/cargo-watch-8.1.1-x86_64-pc-windows-msvc/cargo-watch-8.1.1-x86_64-pc-windows-msvc.tar.gz'
11:00:26 [INFO] This will install the following binaries:
11:00:26 [INFO]   - cargo-watch (C:\Users\taawech0\.cargo\bin\cargo-watch-v8.1.1.exe)
11:00:26 [INFO] And create (or update) the following symlinks:
11:00:26 [INFO]   - cargo-watch (C:\Users\taawech0\.cargo\bin\cargo-watch.exe -> C:\Users\taawech0\.cargo\bin\cargo-watch-v8.1.1.exe)
11:00:26 [INFO] Installing binaries...
11:00:26 [WARN] The binary at C:\Users\taawech0\.cargo\bin\cargo-watch-v8.1.1.exe does already exist, going to overwrite it
11:00:27 [INFO] Installation complete!