feat: MI Assign activity screens (M2-7406)

[farmerpaul]

• Tests for the changes have been added
• Related documentation has been added / updated
• OSS packages added to MindLogger open source credit page

📝 Description

🔗 Jira Ticket M2-7406

Adds informative banners and labels to Activity screens when performing a multi-informant assignment.

• Displays a new banner on the activity welcome screen informing the respondent who the assessment is about
• Displays a label within each item's description (About {{name}}) below any media, and above the first line containing text content

📸 Screenshots

Before	After

🪤 Peer Testing

Note

This feature depends on the enableActivityAssign feature flag. This should already be enabled in dev/local environments. It would also be worth testing this with that feature flag disabled to confirm that existing behaviour is preserved with the MI Assign feature disabled, by adding features.enableActivityAssign = false prior to the return statement here in useFeatureFlags.

Please refer to ticket's AC for the main peer testing steps.

In addition, after completing a multi-informant assigned activity, confirm that the POST to the answers endpoint includes the appropriate targetSubjectId. Also confirm that for self-reports, that property is not included.

[aws-amplify-us-east-1]

This pull request is automatically being deployed by Amplify Hosting (learn more).

Access this pull request here: https://pr-534.d15zn9do8xbzga.amplifyapp.com

[sultanofcardio]

Approved with some minor feedback

---

This is slightly unrelated to this PR, but I noticed that if I start a take now, both sets of UI show up

So we need to add the condition && activityListItem.targetSubject === null to this if statement

mindlogger-web-refactor/src/widgets/ActivityGroups/ui/ActivityCard/index.tsx

Lines 147 to 156 in 26d0036

	useOnceLayoutEffect(() => {
	if (
	context.startActivityOrFlow &&
	((!isFlow && context.startActivityOrFlow === activityListItem.activityId) ||
	(isFlow && context.startActivityOrFlow === activityListItem.flowId))
	) {
	// Pass `true` to ensure activity doesn't resume from a previous progress state.
	onStartActivity(true);
	}
	});

[farmerpaul]

I incorporated your suggestions, @sultanofcardio. Good catch on the interaction of Take Now with MI Assign. It's not just the UI issue you identified that was introduced with MI Assign – Take Now will actually no longer start unless you are assigned (manually or auto) to the activity as a self-report. Since Take Now should take precedence over MI Assign, however, this needs to be fixed. I've created M2-7796 to address this.

[sultanofcardio]

Looks good

[mbanting]

Nice work @farmerpaul. Just one small comment but pre-approving.

Peer tested successfully aside from the badge and banner also showing on Take Now, as @sultanofcardio pointed out. The suggested solution in ActivityCard/index.tsx seems to work, although I'm not entirely sure I understand how? If going with it, I suggest adding a comment so others coming across it understand why && activityListItem.targetSubject === null is needed.

[farmerpaul]

@mbanting incorporated your feedback! Thanks for the 👀