release: cargo-binstall v0.15.0

[github-actions]

This is a release PR for cargo-binstall version 0.15.0 (performing a minor bump).

Use squash merge.

Upon merging, this will automatically create the tag v0.15.0, build the CLI, and create a GitHub release with the release notes below.
You will still need to manually publish the cargo crate:

$ git switch main
$ git pull
$ git switch --detach v0.15.0
$ cargo publish -p cargo-binstall

To trigger builds initially, close and then immediately re-open this PR once.

---

Edit release notes into the section below:

Release notes

Binstall is a tool to fetch and install Rust-based executables as binaries. It aims to be a drop-in replacement for cargo install in most cases. Install it today with cargo install cargo-binstall, from the binaries below, or if you already have it, upgrade with cargo binstall cargo-binstall.

In this release:

• Disable tcp_nodelay and add rate limiting for HTTP requests. This makes installation more reliable, especially when installing many crates at once. (Add option to create delay for downloading from github releases #457, Disable tcp_nodelay for reqwest::Client and add rate limiting for https requests #458)
• Allow --pkg-fmt, --bin-dir, --pkg-url overrides when installing multiple crates. (Support batch installation with overrides --pkg-url and --pkg-fmt #444, Allow batch installation with cli_overrides #454)
• Use CARGO env variable if present. Cargo sets this for subcommands: it is useful when the cargo binary in use may not be in a standard location or in PATH. (Honor environment variable CARGO #452, Use CARGO env variable if present #453)
• Don't try to fetch a package if the crate provides no binaries. This fixes a regression which appeared in 0.14.0. (Fix skipping optional dep: Skip fetcher if they provide 0 bin #446)

Other changes:

• Update README to make it more friendly to beginners. (Update README #464)
• More optimizations. (Refactor and Optimizations #459)
• Bump clap from 3.2 to 4.0 (Update clap requirement from 3.2.22 to 4.0.2 in /crates/bin #447, Update clap requirement from 3.2.22 to 4.0.2 in /crates/binstalk #448, Bump clap from 3.2.22 to 4.0.2 #449, Bump clap to v4.0.2 #450, Bump clap from 4.0.2 to 4.0.4 #451, Bump clap from 4.0.4 to 4.0.8 #456, Bump clap from 4.0.8 to 4.0.9 #460, Bump clap from 4.0.9 to 4.0.10 #461)
• Bump cargo_toml from 0.12.2 to 0.12.4 (Bump cargo_toml from 0.12.2 to 0.12.4 #455)

[NobodyXu]

@passcod Can you check the changelog I wrote to make sure it doesn't miss anything and is clear to the users? Thanks

[NobodyXu]

The CI failed.
I will investigate it tomorrow and I might have to manually release v0.15.0 or just release v0.15.1

[NobodyXu]

I believe this might be related to https://github.com/cross-rs/cross/wiki/FAQ#undefined-reference-with-build-std

[NobodyXu]

Related issues:

• cross 0.2.4 failed to compile libz-ng-sys v1.1.8 on armv7-unknown-linux-gnueabihf cross-rs/cross#1066
• cross 0.2.4 failed to compile detect-wasi on aarch64-unknown-linux-gnu cross-rs/cross#1067

[NobodyXu]

I will probably submit a new PR that disables use of libz-ng for our CI according to this comment from @Alexhuszagh.

Then we would have to do a new patch release.