Merge cache-cargo-install-action

[taiki-e]

As said in #54 (comment), I would like to merge cache-cargo-install-action into install-action.

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...

TODO:

• Switch to composite action #58
• Address the cache-cargo-install-action's limitation that cannot specify multiple crates in a single action call.

[NobodyXu]

Related: The binaries installed via cargo-binstall can also be cached.
cargo-binstall by default, installs binaries to $CARGO_HOME and then updates $CARGO_HOME/.crates.toml and $CARGO_HOME/binstall/crates-v1.json.

So if you cache $CARGO_HOME/{bin, .crates.toml, binstall/crates-v1.json}, then you can also cache result of cargo-binstall if the binaries is up-to-date.

If a new version has released, then cargo-binstall will detect that and upgrade the binaries if the version_requirement is empty (default to *) or *, >=$VERSION, since cargo-binstall would always hit https://crates.io to find out the max_stable_version for the crate.

In the case of upgrade, you can detect that by checking the hash of the .crates.toml and then invalidates the cache.

[NobodyXu]

Regarding $CARGO_HOME, there's one catch though.

There's a PR in cargo-binstall to support install.root in $CARGO_HOME/config.toml cargo-bins/cargo-binstall#884 which can overrides where the binaries are installed and manifests are updated.