microsoft-go-innerloop flaky: no space left on `/`

=== RUN   TestSystemCryptoDefault/windows_amd64
=== PAUSE TestSystemCryptoDefault/windows_amd64
=== CONT  TestSystemCryptoDefault/windows_amd64
    systemcrypto_test.go:171: go build failed: exit status 1
        # strings
       [ compile: writing output: write $WORK/b054/_pkg_.a: no space left on device](https://dev.azure.com/dnceng/internal/_git/5b09aaa7-b9fb-4319-9f84-64b0b85fe520?path=WORK%2Fb054%2F_pkg_.a&version=GBmicrosoft%2Fmain&_a=contents&line=1&lineEnd=2&lineStartColumn=1&lineEndColumn=1&lineStyle=plain)
        crypto: mkdir /tmp/cmd-go-test-3173849885/go-build2788255704/b003/: no space left on device
        # syscall
       [ compile: writing output: write $WORK/b074/_pkg_.a: no space left on device](https://dev.azure.com/dnceng/internal/_git/5b09aaa7-b9fb-4319-9f84-64b0b85fe520?path=WORK%2Fb074%2F_pkg_.a&version=GBmicrosoft%2Fmain&_a=contents&line=1&lineEnd=2&lineStartColumn=1&lineEndColumn=1&lineStyle=plain)
--- FAIL: TestSystemCryptoDefault/windows_amd64 (19.92s)

https://dev.azure.com/dnceng/internal/_build/results?buildId=2934822&view=ms.vss-test-web.build-test-results-tab&runId=56629225&resultId=162416&paneView=debug

Failures are widespread on recent innerloop builds on microsoft/main and may share this root cause:

https://dev.azure.com/dnceng/internal/_build?definitionId=1342&_a=summary&branchFilter=150077%2C150077%2C150077%2C150077%2C150077%2C150077%2C150077%2C150077%2C150077%2C150077%2C150077%2C150077%2C150077%2C150077%2C150077%2C150077%2C150077%2C150077

Perhaps the VM setup was reconfigured in an unexpected way?

Review systemcrypto_test.go around line 171 and the linked microsoft/main innerloop build results; first compare recent failures for the shared no-space condition and inspect the VM setup. Done means identifying the disk-space regression or configuration cause, applying the appropriate CI or VM fix, and confirming innerloop builds no longer fail for this reason.