UI – Updates to confirm invite flow

[jacobshandling]

For #24486

• Check invite validity before rendering form, error if invalid
• Use data returned from validity check to pre-populate form
• Remove dependence of flow on URL params other than token
• Remove other URL params from link generated in invite confirmation email
• Refactor form from JS to TS
• Refactor form from class to functional components
• Cleanup unused logic
• Improve error handling

Invalid invite

Valid invite

• Changes file added for user-visible changes in changes/
• Updated tests
• A detailed QA plan exists on the associated ticket (if it isn't there, work with the product group's QA engineer to add it)
• Manual QA for all new/changed functionality

[jacobshandling]

This just calls lodash's isEqual. Using here for consistency but perhaps we can retire this function in favor of calling the lodash method directly.

[codecov]

Codecov Report

Attention: Patch coverage is 93.18182% with 3 lines in your changes missing coverage. Please review.

Project coverage is 63.55%. Comparing base (b0de218) to head (8ceca36).
Report is 11 commits behind head on main.

Files with missing lines	Patch %	Lines
...ents/forms/ConfirmInviteForm/ConfirmInviteForm.tsx	95.34%	2 Missing ⚠️
frontend/utilities/endpoints.ts	0.00%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #25583      +/-   ##
==========================================
- Coverage   63.60%   63.55%   -0.06%     
==========================================
  Files        1624     1621       -3     
  Lines      155419   154818     -601     
  Branches     3967     4023      +56     
==========================================
- Hits        98856    98387     -469     
+ Misses      48761    48670      -91     
+ Partials     7802     7761      -41     

Flag	Coverage Δ
frontend	53.14% <93.18%> (+0.06%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[sgress454]

Code looks good, tested 👍

One suggestion would be to add a retry function to the useQuery invocation. Right now it sits there spinning and retries four times even when the API response is a 404 -- it'd be better to have it show "invalid form" immediately.

[ghernandez345]

can we not use the issue number only as the branch name. git gets confused when I try to switch to this branch cause it thinks I'm trying to check out a commit.