has anyone else noticed that `cargo binstall` in GitHub workflows sometimes gets 403 responses from the GH API when checking for releases to download and then has to fall back to compiling from source (which of course takes forever)? i think this is related to the rate limit which GH introduced for unauthenticated calls - i'm just surprised that API calls from their own action runners (this isn't even a self-hosted one) wouldn't be excluded from that?!

example:
```
Run cargo binstall -y cargo-nextest
 INFO resolve: Resolving package: 'cargo-nextest'
 INFO has_release_artifact{release=GhRelease { repo: GhRepo { owner: "nextest-rs", repo: "nextest" }, tag: "cargo-nextest-0.9.99" } artifact_name="cargo-nextest-0.9.99-x86_64-unknown-linux-gnu.tar.gz"}:do_send_request{request=Request { method: GET, url: Url { scheme: "https", cannot_be_a_base: false, username: "", password: None, host: Some(Domain("api.github.com")), port: None, path: "/repos/nextest-rs/nextest/releases/tags/cargo-nextest-0.9.99", query: None, fragment: None }, headers: {"accept": "application/vnd.github+json", "x-github-api-version": "2022-11-28"} } url=https://api.github.com/repos/nextest-rs/nextest/releases/tags/cargo-nextest-0.9.99}: Received status code 403 Forbidden, will wait for 120s and retry
 WARN resolve: Timeout reached while checking fetcher invalid url: deadline has elapsed
 WARN resolve: Timeout reached while checking fetcher invalid url: deadline has elapsed
 WARN resolve: Timeout reached while checking fetcher QuickInstall: deadline has elapsed
 WARN resolve: Timeout reached while checking fetcher QuickInstall: deadline has elapsed
 WARN The package cargo-nextest v0.9.99 will be installed from source (with cargo)
[..]
```