Implement non-registered user alert on my-health tools

[wesrowe]

Description

User story

As an authenticated user who is not registered to a VA facility, I want health apps within the /my-health/ portal on VAgov to alert me to the fact that I don't have access to health tools, so that I have enough information to take action if appropriate.

Notes

• Design ~and permission from tool teams~ covered in #75533.
• See Mural
• Implementation does not need to catch child pages
• Jim recommendation: consider a route guard
  • Users wouldn't even reach the tool landing page if they tried to get there (e.g. hacked the url)

Possible tasks:

• [separate PRs per tool?]
• a11y review

Acceptance criteria

• [x] Get permission from tool POs before implementing – achieved in this slack thread on 3/19/2024
• [x] Users cannot access individual tool pages or any content deeper than the MHV landing page. Instead, route guards will send all users who access links or side doors to URLs within/my-health to the main landing page, where users will see the alert already in production on this page.
• [x] Content of alert is updated per comment below (replace both with at least one)
• [x]

Associated PRs:

1. Add mhv route guard to after visit summary - MERGED
2. Add mhv route guard to medications - 2 Approvals needed, 1 from our team
3. Add medical records mhv route guard - 2 Approvals needed, 1 from our team
4. Add mhv route guard to Secure Messaging - CLOSED due to Oracle migration which will bring in users that don't rely on the vets-api
5. Add mhv route guard to supply re-ordering - 2 Approvals needed, 0 from our team
6. Add route guard component and unit test and copy for NoHealthAlert - MERGED

[wesrowe]

refine after design is complete – may be complex (eg H1 challenge)

[wesrowe]

I removed the blocker on this one, as Sara's work on the non-registered alert is complete. (I.e., no controversy or questions around that section of the mural.)

[wesrowe]

Sara to message tool owners for permission for this work.

[wesrowe]

update: as linked in first AC, Sara got sign-off in slack from MHV stakeholders about using the route-guard idea for un-registered users – i.e. taking any un-registered user from the tool page they tried to access to the MHV landing page with the un-registered alert. Biggest point of discussion was Appointments edge case around claim exams (aka compensation and pension exam).

[sterkenburgsara]

Per Lauren Alexanderson & Laura Willwerth in Slack, there is a slight update to the alert we need to make in production: update the text in the first line of the alert to say "at least one."

[jzucadi]

Secure messaging currently has a validation process for showing an alert to users based on backend services aka the vets-api. The route guard PR was closed due to an upcoming Oracle migration which will bring in a new set of users that do not have the mhvAccountState property in the vets-api

[LynneJohnson224]

@wesrowe @jzucadi my notes from planning yesterday were that we will close this ticket and address the issues in 2 new tickets. Can we close this?