test(app-project): mock Zooniverse APIs in stories with MSW

[eatyourgreens]

• install MSW for the storybook.
• add a mock API to the workflow selector stories.
• add mock APIs to the subject picker stories.
• skip a couple of Mocha tests that now fail with errors. all the tests should still pass.

Package

• app-project

Linked Issue and/or Talk Post

• companion to fix(app-project): data-fetching for assigned workflow level #6219.
• adds a story to test Workflow Assignment: if current assigned workflow is complete, locked/unlocked split fails #6198.

How to Review

Running the dev storybook locally, there are a couple of new stories:

• the subject picker now shows mock data in the browser!
  http://localhost:9001/?path=/story/project-app-shared-subject-picker--default

• the workflow selector has a story that tests the case where an assigned workflow is complete, and is fetched from the Panoptes API (Workflow Assignment: if current assigned workflow is complete, locked/unlocked split fails #6198.) It unlocks levels 1 and 2, even though 3 is complete and not available. Level 4 remains locked.
  http://localhost:9001/?path=/story/project-app-shared-workflow-selector--missing-levels

You can test the deployed storybook (NODE_ENV=production) with:

yarn build-storybook
npx serve ./storybook-static

I've skipped a couple of tests that are failing with errors. I'm not sure why they fail. I think it might be happening because stories are designed to run in a browser, but the tests run in Node. Mocha tests, with nock to mock the Panoptes API in Node, should still run and pass on this branch.

Checklist

PR Creator - Please cater the checklist to fit the review needed for your code changes.
PR Reviewer - Use the checklist during your review. Each point should be checkmarked or discussed before PR approval.

General

• Tests are passing locally and on Github
• Documentation is up to date and changelog has been updated if appropriate
• You can yarn panic && yarn bootstrap or docker-compose up --build and FEM works as expected
• FEM works in all major desktop browsers: Firefox, Chrome, Edge, Safari (Use Browserstack account as needed)
• FEM works in a mobile browser

[coveralls]

coverage: 77.838% (-0.006%) from 77.844%
when pulling 6b8c9d9 on eatyourgreens:project-msw-mocks
into 5d3e4aa on zooniverse:master.

[eatyourgreens]

I've used the same config here that I use to test client-side React components with Storybook 8, so this should be forward compatible.

[eatyourgreens]

This is needed in Storybook 7, but 8 handles it automatically for you.

[goplayoutside3]

Phew 😌 I messed up there for a minute by pushing changes before including the latest dependency bumps from the master branch.

I made two changes:

1. Per fix(app-project): data-fetching for assigned workflow level #6219 (comment) I changed the SWROptions in useAssignedLevel() to revalidate on mount. Previously, the WorkflowSelector story on this branch did not properly unlock Levels 1+2 when the user is assigned a workflow id of an inactive workflow with level 3.
2. I made some updates to the WorkflowSelector stories to use a select with options for userReadyState (its options array was incorrectly configured) and I renamed the two stories that use the workflow assignment feature to reflect the name of that feature.