feat(cache): Mention when a download failure is due to insufficient permissions

[relaxolotl]

If we know that the reason why we weren't able to download a file was due to permissions we now record that fact and return it in the symbolication response.

This bases itself off of #512 to avoid conflicts with the download error work that's currently open in PRs.

[Swatinem]

lgtm, but please run some tests through sentry to make sure it can deal with these noperm errors. we ran into a couple of situations where we broke sentry because we changed the results that we return, and the validation for these is quite strict.

[relaxolotl]

@Swatinem:

please run some tests through sentry to make sure it can deal with these noperm errors.

I quickly ran through some example errors in my local build of sentry to make sure nothing broke, but I believe armenzg very kindly added in integration tests to our pipeline to catch these sorts of errors, i.e. if this https://github.com/getsentry/symbolicator/runs/3349120741 job is passing we are good.

[Swatinem]

I don’t think we have an integration test specifically for this. Might be a good idea to add one though. Just configure an obviously bogus s3 source, and see that surfaces the permission error. Though not sure if S3 gives you different errors if you provide a completely bogus bucket, or just if the keys are invalid.

[relaxolotl]

also checked this locally to make sure sentry didn't reject the new-ish payload, and i can confirm that it does not (and it even mentions "permission")

[Swatinem]

nice! so the UI was able to deal with these statuses after all ;-)