Fix window release

[Jake-Shadle]

So I'm making my own releases on my fork for now, and I noticed only Windows was failing (when trying to use GCS), which turned out to be because only the default features (s3) were enabled. I thought this was weird because looking at appveyor, it should be using --features="all" at a minimum, but the actual executable in the tarball wasn't. It seems that the target/release/sccache.exe that was being tarballed was actually one that got overwritten by cargo test, not the one that was built initially with just cargo build. This was still super confusing, because...cargo test is supposedly using the same flags. I don't really know the root cause of this issue and am frankly tired of iterating on CI stuff, so I just did a quick fix to rerun the normal release build before doing the rest of the release deployment, which correctly enables all the features, and doesn't really add to much to build time because the intermediate rlibs are already all built and ready to go so it just needs to relink the executable.

¯\_(ツ)_/¯

[luser]

I believe the root cause here is that we use escargo to run sccache via cargo run and it's not propagating the list of enabled features down. This comment seems to indicate that's the case.