[Feat] Add support for cargo binstall

[GZTimeWalker]

Try to add support forcargo binstall?

You can refer to https://github.com/cargo-bins/cargo-binstall/blob/main/SUPPORT.md

[Dj-Codeman]

I don't really understand why I would. cargo install works perfectly fine. So long as I don't forget the almighty cargo publish new versions, there isn't any additional work i need to put into packaging or anything with it.

[GZTimeWalker]

I don't really understand why I would. cargo install works perfectly fine. So long as I don't forget the almighty cargo publish new versions, there isn't any additional work i need to put into packaging or anything with it.

The proposal of cargo binstall is to release these cargo packages in pre-compiled binary form. Source code compilation is great, but not everyone is willing to waste time and disk space on recompilation. Therefore, many packages now pre-compile during release through actions, such as cargo cache and cargo install-update.

[Dj-Codeman]

I gotta give this a try on windows when I get the chance. I think because my build targets are so broad it's not picking up the right bin. I'm working on it tho

[Dinnersteak]

@Dj-Codeman How's the cargo bin install coming along?

[goto-dev-null]

It seems like it works, with warnings, for me - using cargo-binstall 1.17.9 and cargo 1.94.0.

⋊> ~ cargo binstall dns-doge                                                                                                                                                                     18:10:17
 INFO resolve: Resolving package: 'dns-doge'
 WARN Failed to render url for Context {
    name: "dns-doge",
    repo: None,
    target: "x86_64-unknown-linux-gnu",
    version: "0.2.9",
    archive_format: None,
    binary_ext: "",
    subcrate: None,
    url: None,
    ..
}: Failed to render template: missing key `repo`
 WARN Failed to render url for Context {
    name: "dns-doge",
    repo: None,
    target: "x86_64-unknown-linux-musl",
    version: "0.2.9",
    archive_format: None,
    binary_ext: "",
    subcrate: None,
    url: None,
    ..
}: Failed to render template: missing key `repo`
 INFO resolve: Verified signature for package 'dns-doge-0.2.9-x86_64-unknown-linux-gnu': timestamp:1759703271   file:dns-doge-0.2.9-x86_64-unknown-linux-gnu.tar.gz     hashed
 WARN The package dns-doge v0.2.9 (x86_64-unknown-linux-gnu) has been downloaded from third-party source QuickInstall
 INFO This will install the following binaries:
 INFO   - doge => /home/muhuser/.cargo/bin/doge
Do you wish to continue? [yes]/no y
 INFO Installing binaries...
 INFO Done in 12.21251866s
⋊> ~ /home/muhuser/.cargo/bin/doge --version --version                                                                                                                                                                              18:10:34
doge  command-line DNS client
v0.2.9
https://dns.lookup.dog/

I think that the repo warnings are just because the crates.io entry does not specify a repo, but it does still install doge. AFAIK crates.io just pulls that from the Cargo.toml, so I created #92 to address that and silence the warning.