[Feature Request] Support cargo binstall for release artifacts

[bb010g]

pacaptr currently publishes pre-built artifacts with each release, but cargo binstall isn't aware of these artifacts, making cargo binstall pacaptr fail. See https://github.com/cargo-bins/cargo-binstall/blob/main/SUPPORT.md.

You can implement support via [package.metadata.binstall] keys in the crate manifest or via changing the artifact file name scheme to something cargo binstall will auto-detect. To see everything currently tried, try cargo binstall --log-level debug pacaptr. Specifying artifacts in the crate manifest should be preferred, as auto-detection requires querying the GitHub API about each tested artifact filename.

[rami3l]

@bb010g Thanks for filing this issue! I'll definitely have a closer look when I'm available.

[rami3l]

@bb010g The binary names are generated by GoReleaser (which uses the Golang naming convention instead of the Rust ones), and I'm reluctant to change that again.

Thanks to your pointers, I have made the required additions in Cargo.toml, but I'm not sure if this will work correctly.
Would you mind reviewing my changes in #653 and, if possible, test the new manifest with something like the following?

cargo binstall pacaptr --manifest-path ./Cargo.toml --dry-run --log-level=debug

Many thanks!