Prevent Windows GHA CI disk exhausation

[DellaBitta]

Windows BoringSSL builds are now larger due to #454. The checkout & build partition (D:) hits capacity when attempting to install the Google Cloud SDK, which is what we use to upload the final integraion_test build artifacts to storage.

This change moves the arhives destined for GCS to the C: drive, then installs the Cloud SDK after they're off of D:. The migration of the integration tests only occurs on Windows, for now.

Some notes:

• We can’t set the build_testapps.py’s --output_directory flag to directly output to the C: directory because python’s relpath operations fail when working across different drives.
• The github.workspace env var can be changed to override check-out & installation paths, but the GHA team notes potential unknown side effects. Therefore I didn’t test this.
• We couldn't use mv the results to C: as Firestore's build results include symlinks. Using tar to ferry the files instead.

[github-actions]

✅  Integration test succeeded!

Requested by @DellaBitta on commit d7b7a13
Last updated: Tue Jun 15 12:06:11 PDT 2021
View integration test results

[vimanyu]

Thanks for taking care of this! One minor note but LGTM otherwise.

[vimanyu]

Just for readability, could you put a comment here what the "ta" directory is? Others are easy to follow.

[vimanyu]

Just a note, the boringssl change (download tarball -> checkout specific tag in repo) increased the boringssl source code directory size from 100M to 280M.

[jonsimantov]

Just a note, the boringssl change (download tarball -> checkout specific tag in repo) increased the boringssl source code directory size from 100M to 280M.

Would checking out with --depth 1 help this?

[DellaBitta]

I'm going to try out some new git cleanup code that I've found to see if I can reduce the size of the checkout, but I'd like to merge this for now so that we can effectively use integration tests moving forward and I can roll back this change if it's not necessary for now.