chore(other): enable cargo binstall

[slowsage]

Why

This is needed since the crate name and archive prefix differ.
Related: #45

[KeisukeYamashita]

Thank you very much for your PR,
let me check this on the weekend!

[KeisukeYamashita]

Hello, thanks for your PR.

Do you have any reason why you want to add this? I don't see any errors while running cargo install or cargo binstall on my local environment:

$ cargo binstall  commitlint-rs@0.1.9 --force 
 INFO resolve: Resolving package: 'commitlint-rs@=0.1.9'
 WARN The package commitlint-rs v0.1.9 will be installed from source (with cargo)
Do you wish to continue? yes/[no]
? yes
  Downloaded commitlint-rs v0.1.9
...
   Replacing /Users/keke/.cargo/bin/commitlint
    Replaced package `commitlint-rs v0.1.10` with `commitlint-rs v0.1.9` (executable `commitlint`)
 INFO Cargo finished successfully

[slowsage]

Weird. For me, I get:

cargo binstall  commitlint-rs@0.1.9 --force 
 INFO resolve: Resolving package: 'commitlint-rs@=0.1.9'
 WARN The package commitlint-rs v0.1.9 will be installed from source (with cargo)
  Downloaded commitlint-rs v0.1.9
  Downloaded 1 crate (25.0 KB) in 0.04s
    Updating crates.io index
  Installing commitlint-rs v0.1.9
    Updating crates.io index
   Compiling proc-macro2 v1.0.82
   Compiling unicode-ident v1.0.12
   Compiling autocfg v1.3.0
   Compiling libc v0.2.154
   Compiling memchr v2.7.2
   Compiling futures-sink v0.3.30

cargo-binstall v1.6.5

Not sure if it downloaded the binary directly from your log.
The below line (with the new Cargo.toml) will skip the compile and download the binary directly.
cargo binstall --manifest-path ./Cargo.toml commitlint-rs

[KeisukeYamashita]

Ah, sorry...I misread the log and found it was trying to build it from the source.

Thank you very much, LGTM!

[KeisukeYamashita]

Let me update the scope of the PR as ci is not allowed 🙏