Use cargo-binstall batching mode

[taiki-e]

Closes #44

[taiki-e]

hmm https://github.com/taiki-e/install-action/actions/runs/3923398658/jobs/6706983450

WARN The package watchexec-cli v1.21.0 will be installed from source (with cargo)

[NobodyXu]

hmm https://github.com/taiki-e/install-action/actions/runs/3923398658/jobs/6706983450

WARN The package watchexec-cli v1.21.0 will be installed from source (with cargo)

That could be switched off using --disable-strategies compile

[NobodyXu]

hmm https://github.com/taiki-e/install-action/actions/runs/3923398658/jobs/6706983450

WARN The package watchexec-cli v1.21.0 will be installed from source (with cargo)

That's really strange because watchexec-cli v1.21.0 indeed provides musl build for x86_64.

[NobodyXu]

@taiki-e I tried installing this from my own laptop and it works fine:

❯ cargo binstall watchexec-cli --targets x86_64-unknown-linux-musl
 INFO resolve: Resolving package: 'watchexec-cli'
 WARN The package watchexec-cli v1.21.0 will be downloaded from github.com
 INFO This will install the following binaries:
 INFO   - watchexec (watchexec -> /Users/nobodyxu/.cargo/bin/watchexec-v1.21.0)
 INFO And create (or update) the following symlinks:
 INFO   - watchexec (/Users/nobodyxu/.cargo/bin/watchexec -> watchexec-v1.21.0)
Do you wish to continue? yes/[no]
? no
 WARN Installation cancelled

[taiki-e]

That could be switched off using --disable-strategies compile

Hmm, it would be a breaking change...

That said, if installing from source, it is better to cache the binaries, so the fallback that installs from source is not very good to me.

So I'm considering outputting info message suggesting cache-cargo-install-action in all officially unsupported cases. (Originally, I was considering outputting it when the installation fails)

Ideally, I would like to merge cache-cargo-install-action into install-action, run cargo-binstall with --disable-strategies compile, and use cache-cargo-install-action when the installation fails, though...

[NobodyXu]

Hmm, it would be a breaking change...

Yes, so better to fix it in cargo-binstall.

Ideally, I would like to merge cache-cargo-install-action into install-action, run cargo-binstall with --disable-strategies compile, and use cache-cargo-install-action when the installation fails, though...

That sounds awesome!