Blocked by#1184
Fixes#734

• Adds New User button to the Users page
• Adds Create User page
• XState determines if it's a field error or a generic error
• I'm pretending users come with org ids in preparation forBruno's PR
• I use aselector to get the org id out of theauthXService without making theCreateUserPage re-render forevery change toauthXService
• Note that theCreateUserForm stories have a flash of a validation error message. That appears to be a Storybook problem where it thinks the field istouched momentarily, maybe a lag from looking at a related story.
• Note that in order to see the field error message under test in the FormErrors story, you have to touch the email field.
• I gave up on testing for redirect after success because it was taking too long. We should e2e test redirects after the deadline.
• I got rid of creation mode in the XService because it expanded the surface area for bugs by requiring routing and the XService to stay in sync. So I'm embeddingnavigate in an action like@BrunoQuaresma suggested. I prefer this over embedding it incontext because in the latter solution, the XService has to know our routes.
• I had to resort to a jest mock for the generic error because other ways of mocking a non-response error either caused a crash or caused MSW to fall back to its happy path handler.