Spike: Remapping upstream errors to communicate with the app better

[timwright12]

Description

We get a lot of upstream errors affecting the mobile app, some expected, some not, but it makes it look like the app isn't working when in fact it's just an upstream service having an issue or being in the middle of a maintenance window. We would like to see if it's feasible to remap these 5XX errors to 200 errors paired with a custom message to improve the in-app experience.

Acceptance Criteria

• [ ] Ticket description (above) has been reviewed, updated, and approved by @DonMcCaugheyUSDS (check off when complete)
• [ ] Documentation on whether we can do this or not
• [ ] Create any needed follow up tickets to complete potential work

[timwright12]

@DonMcCaugheyUSDS I assigned this to you as the first acceptance criteria item, once done you can just remove yourself as an assignee

[jperk51]

We are already taking steps to differentiate between upstream and our API errors. Our errors are pretty much exclusively 500 errors while upstream errors are usually 502 or 503. I wouldn't recommend mapping them to 200s. We should be able to achieve anything we want given the current, more accurate, error codes.