add Sentry logging to narrow down failure mode

[Mitch-A6]

Note: Delete the description statements, complete each step. None are optional, but can be justified as to why they cannot be completed as written. Provide known gaps to testing that may raise the risk of merging to production.

Summary

• This work is behind a feature toggle (flipper): NO
• Add exception-catching blocks around each of the steps of this action, logging any errors to Sentry
• It's not clear why these 403 errors are coming up, and I hope a more specific understanding of their origin will help.
• Health Enrollment 10-10EZ/CG team

Related issue(s)

Ticket: department-of-veterans-affairs/va.gov-team#92139

Testing done

I ran the app locally and confirmed that the upload process works; since this is a logging change only, there's no testing to add.

What areas of the site does it impact?

• This only affects Sentry logging for File Upload failures

Acceptance criteria

• No error nor warning in the console.
• Events are being sent to the appropriate logging solution
• No sensitive information (i.e. PII/credentials/internal URLs/etc.) is captured in logging, hardcoded, or specs

[JoshingYou1]

LGTM!

[github-actions]

Backend-review-group approval confirmed.

[Mitch-A6]

deleted resolved comment on app/controllers/concerns/form_attachment_create.rb:22 to enable merging:

coope93 4 days ago
Looks like you don't need begin here as it is redundant. Once these are cleaned up it looks good to go 👍