Pages Editor: implement Associated Subject Sets & fetch more data

[shaunanoordin]

PR Overview

Part of: Pages Editor MVP project and FEM Lab super-project Follows #7046 Staging branch URL: https://pr-7048.pfe-preview.zooniverse.org/lab/1982/workflows/editor/3711?env=staging

This PR implements the "Associated Subject Sets" feature on the Workflow Settings sub-page.

• New component: AssociatedSubjectSets.
• New behaviour/feature: on Pages Editor (for any Workflow) -> Workflow Settings...
  • The Associated Subject Sets feature should list all Subject Sets available to the Project (caveat: up to a max of 250. Paging may be a future problem to solve.)
  • The Associated Subject Sets feature (and no, I will not shorten it to an acronym) should show which Subject Sets are linked to the Workflow via ticked checkboxes.
  • Clicking on the checkboxes should link/unlink Subject Sets to/from the Workflow.

Also, some background work was required to fetch the Subject Sets, so the DataManager was updated as well.

• Updated behaviour: DataManager now fetches the project resource.
• Misc update: the Preview Workflow link now works as intended.

Screenshot: example workflow with 3 available subject sets, 2 of which are linked.

Testing

• Open the staging URL. You should be looking at a test workflow (e.g. staging wf 3711)
• Click on the Workflow Settings tab/button to view the sub-page.
• Look for the Associated Subject Sets feature.
  • It should list all available subject sets, and show which ones are already linked.
  • Click on a subject set to link/unlink them
  • Reload the page to confirm
  • Expectation: you should be able to link or unlink as many sets as you want. Changes should be committed to Panoptes.

Status

Ready for review!

This PR is currently targeting pages-editor-pt14 for review purposes. Do not merge until 6974 is ready and this branch's merge is re-targeted to master.

[shaunanoordin]

Thanks Travis! I'm going to rebase, then address some of the smaller feedback in this PR, before merging. 👍

To respond to the point you raised:

I expected refreshing the page to keep me on the same tab "workflow settings".

Good point. Perhaps ideally, each "tab" should be its own sub-page with a URL, like https://local.zooniverse.org:3735/lab/1982/workflows/editor/3711/workflow-settings. However, at the moment the constraint I've imposed on myself is that the PagesEditor should be as self-contained as possible, so using a single path (/lab/PROJECT_ID/workflows/editor/WORKFLOW_ID) for all the PagesEditor tabs/sub-pages/features allows me to side step adding router dependencies inside the PagesEditor (which would've been somewhat annoying should we plan to port this to FEM.)

EDIT: Wait, a thought occurs: ?tab=workflowSettings param instead of /workflow-settings subpath to circumvent having to use react-router? Worth experimenting with later.

[coveralls]

coverage: 56.98%. remained the same when pulling 8dc7206cb7de4fbafc35010ef72f188add4830fd on pages-editor-pt15 into a8bcd3da1310eab67f0218e49f6f1398d66f3ba2 on master.