New Confirmation Page: Non 200 submission status testing

[christinec-fftc]

Issue Description

Handle non 200 (error) scenarios from submission_status. For each of these, we should still display the green success alert since failure notification will come via email. Likely no code changes here, just testing.

Dependent on

• New Confirmation Page: Successful submit flow (with claim id, less than 30 seconds) - part 2 #95237
• New Confirmation Page: Not completely successful submit flow (no claim id) #95241

Tasks

• Mock up a non-200 response from vets-api
• Test scenarios for different http codes, as needed

Based on docs here
401 unauthorized
403 forbidden
404 no record found
500 or any other non 200?

mocks: https://www.figma.com/design/qyTtKDOTHZPGU59PAfqVhq/(526ez)-New-Confirmation-Page-and-Email-Touchpoints?node-id=8405-81028

Acceptance Criteria

• Verify success alert is displayed and yellow alert does not display.

[aurora-a-k-a-lightning]

during testing for
#95241
department-of-veterans-affairs/vets-website#33012

i tested throwing a 500 error:

• frontend polled 3 times
• got 500 internal server error each time
• on the third poll, frontend pushed forward to new confirmation screen with green box, no claim id version (expected)!

[christinec-fftc]

Found a similar response as ahay's notes above, testing with 401, 403, 404 and 500 response codes video