"Classify this Subject" feature: use live active Workflow data

[shaunanoordin]

PR Overview

Our recent experience with the Stereovision project has highlighted the following issues:

• Workflows can be activated and/or inactivated without warning, causing a mismatch in hardcoded project configs.
• Subjects can be de-associated from workflows, making them impossible to Classify (i.e. the subject sets they belong to can be de-associated from active workflows, such as the case with beta test Subjects)

This PR attempts to address the issues above by pulling live active Workflow data for a given Project, and ensuring a Subject "belongs" to at least one active

• ProjectContainer and AppStore:
  • now fetches all active workflows belonging to a Project.
  • Note: this data fetch is considered secondary, and won't block the app from running while it's still ongoing in the background. This is because the WF data is only needed for the "Classify this Subject" feature.
• WorkflowSelectionDialog:
  • lists all active workflows that a Subject is associated with
  • The list of valid workflows is done by comparing active_workflow.links.subject_sets and subject.links.subject_sets; if there's at least one matching subject set, then a volunteer can classify that Subject on that Workflow.

Also:

• documentation updated to reflect current format of project configs in projects.json

Screenshot: WorkflowSelectionDialog after clicking "Classify this Subject" on a Stereovision Subject

Screenshot: similar to above, but the Subject is a test subject that's not associated with any active workflows

Future ideas: since we know the completeness of each live workflow, we can also grey out workflows that are complete. The screenshot below demonstrates how this might look like, and the feature is already partially implemented in the code. (We're just missing good design, and actually completed workflows to test it.)

NOTE: these changes, when deployed, will only affect the Stereovision project. We could easly apply these changes to How Did We Get Here by changing the project config if we wanted, but I'll try my best to not disturb older projects.

Status

Ready to go, but do NOT merge and deploy until we get the green light. We don't want to deploy major feature changes while the Stereovision team is still getting a feel for the Community Catalog

[shaunanoordin]

I've confirmed on Slack that we're good to go! Merging and deploying now.