Avoid `cargo install --force` in CI

[grtlr]

Bug description

Currently, we always run cargo install --force when installing binary crates, skipping already cached versions. Without --force cargo may throw an error depending on the state of the CI's cache.

Expected behaviour

Binary crates should be cached in CI to avoid longer build times.

Fix

@lmy441900 found a solution to this problem. To gist is to also cache ~/.crates.toml, which gets rid of the cargo errors when --force is not used.