AC-api: Implement MHV Landing Page for 4 "user-action" errors

[wesrowe]

Description

User story

As a Veteran for whom the MHV Acct Creation API returned an error requiring MHV Help Desk intervention, I want to be informed on the MHV Landing Page of the issue, which tools are affected, what number to call, and what error code to tell them, so that I can get it resolved efficiently.

Notes

• design completed in Validate acct-creation API discovery against actual in staging #91876 for error codes that require user action to resolve (i.e., call MHV help desk)
• Mural area breaking these out
• Figma link
• Identity team docs on MHV Account Creation
  • Draft docs for /v0/user/mhv_user_account

Screenshot

Possible tasks:

• CONFIRMED: we have to make an API call to get it
• Add new alert for user-facing errors returned from the Account Creation API
• This alert will conditionally reveal the specific error codes that require the user to take an action (call the My HealtheVet helpdesk) to resolve the problem.

Acceptance criteria

• Loading indicator displays while awaiting API response
• Red alert displays if any of the 4 error codes are returned (below) & conditionally reveals the error code # in the alert heading & body content:
  • 801
  • 805
  • 806
  • 807
• Gray boxes for SM, Meds and Records display error instead of links (and icons in headings change to reflect the "error" icon)
• Alert records event to GA4 with heading metadata (similar to e.g. "Register" alert)
• Remove the current 'Register wtih My HealtheVet" alert for users who see these 4 alerts.
• QA review
• A11y review

[wesrowe]

Planning: estimate to 8 if there's an API call required to get the error code

[dcloud]

@kjsuarez We do need to make an API call to get the errors, per this MHV User Account API doc.

We also need to add a Loading Indicator given this API could take many seconds in worst case, and we want to indicate to the user that we are checking for MHV account

[kjsuarez]

Branch
PR

[wesrowe]

I just added an AC to make sure a GA4 event is triggered when the alert renders, similar to other alerts on the page.

[kjsuarez]

vets-api feature flipper PR

[kjsuarez]

For QA testing on local machine

• Mock feature flipper
  • src/applications/mhv-landing-page/mocks/api/feature-toggles/index.js:7
• Mock mhvAccountState data
  • src/applications/mhv-landing-page/mocks/api/user/index.js:67
• Mock API response
  • src/applications/mhv-landing-page/mocks/api/index.js:20

[wesrowe]

@kjsuarez, I thought at one point you considered implementing both ACapi alerts in one PR – the original one in this ticket PLUS the "technical" error one in #98360?

I just want to get a handle on where we are. I looked at the PR linked higher up here, only saw one alert screenshot. And the second story is sitting in Next Sprint.

[kjsuarez]

I had considered handling both kinds of errors as a single PR, but considering the size of the PR as it stands I think it would be a good idea to keep these as separate tickets.

[mcarterA6]

Moving this ticket to Sprint 47.

[allanto-ah]

Environment: Staging

Verified that error codes, 801, 805, 806, 807, generates a specific error code alert on the MHV landing page.

Regression testing was also done to ensure that nothing broke:

1. Verified that the error code didn't shown for a newly created account
2. Verified that existing test users was able to login as expected and didn't run into any issues

[allanto-ah]

Environment: Staging

Verified that these alerts appear in GA4