curl errors on windows (CRYPT_E_REVOCATION_OFFLINE): option to pass --ssl-revoke-best-effort to curl?

[ochafik]

Hi! I'm getting a high rate of failures on windows runners w/ curl: (35) schannel: next InitializeSecurityContext failed: CRYPT_E_REVOCATION_OFFLINE (0x80092013) - The revocation function was unable to check revocation because the revocation server was offline.

example failed runs: on llama.cpp, on minja.

Show error trace

"C:\Program Files\Git\bin\sh.exe" -xc "curl -L 'https://github.com/mozilla/sccache/releases/download/v0.7.6/sccache-v0.7.6-x86_64-pc-windows-msvc.tar.gz' | tar xzf - -O --wildcards '*/sccache.exe' > 'C:\Users\runneradmin\.cargo\bin\sccache.exe'"
  + curl -L https://github.com/mozilla/sccache/releases/download/v0.7.6/sccache-v0.7.6-x86_64-pc-windows-msvc.tar.gz
  + tar xzf - -O --wildcards '*/sccache.exe'
    % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                   Dload  Upload   Total   Spent    Left  Speed
  
    0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
    0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
  curl: (35) schannel: next InitializeSecurityContext failed: CRYPT_E_REVOCATION_OFFLINE (0x80092013) - The revocation function was unable to check revocation because the revocation server was offline.
  
  gzip: stdin: unexpected end of file
  tar: Child returned status 1
  tar: Error is not recoverable: exiting now
  Error: Restoring cache failed: Error: The process 'C:\Program Files\Git\bin\sh.exe' failed with exit code 2

Since this seems to be transient Windows infra errors (maybe experiencing a flare these days), wonder if ccache-action could get an option to pass Windows-only CURL flags --ssl-revoke-best-effort or --ssl-no-revoke? (Also see curl/curl#12239 for more background)

Part of the problem is the curl.exe that ships w/ Git for Windows relies on schannel for SSL. Installing another curl version that doesn't (e.g. through choco install curl --yes, putting it in the path somehow or allowing specifying the exact path to curl as an option) might also potentially solve the issue.

(note: doesn't seem to be the same as #184)