Add a more useful error message when we cache a broken tarball

[sandlerr]

Summary

It looks like there should be an error handler that reports English for the fetchErrorCorrupt string, but instead an error from tar-stream is being returned without the filename.

This makes it quite difficult to figure out which module is causing the error so that the bad tarball can be deleted.

Test plan

Running yarn upgrade <list_of_modules> with this code yielded the following results:

error An unexpected error occurred: "Invalid tar header. Maybe the tar is corrupted or it needs to be gunzipped? (/Users/rsandler/Code/zendesk/zendesk_console/npm-packages-offline-cache/detect-browser-1.7.0.tgz)".

Where previously the section in brackets was not there.
The cause appears to be yarn caching the npm registry's 404 response (which is HTML) to a file. Why it does that, and why the registry is returning 404 for extant modules is not clear to me.