#588 Add a graded assessments feature

[seidior]

Proposed changes

This pull request resolves #588 by launching the first version of our graded assessments feature, allowing program facilitators to assign assessments with either single-choice (multiple-choice, single-response) or free-response questions for program participants to fill out, with the facilitator able to then grade the submission afterward. This is the cumulative work and contributions of OpenTree's fifth cohort of the Professional Mentorship Program.

In this version, program participants can view all assessments for a program, create a new submission for a given assessment (assessments support multiple submissions from a given participant), resume an in-progress submission (with auto-save), and expire or submit an in-progress submission.

In this version, program facilitators can view a list of all submissions for a given assessment from all program participants (in-progress, submitted, expired, or graded).

Pushed for a future version:

• Participants able to view the correct answers and the grades on individual questions, as well as feedback from the grader. (Supported in DB.)
• Facilitators able to grade the participants' assessment submissions. (Supported in DB.)
• Facilitators able to create a new assessment, edit an existing assessment, or delete an assessment. (Supported in backend.)
• Participants able to enroll in a program or users being assigned to facilitate a program (a link to enroll as a participant in the demo program is provided for demonstration purposes though).
• Participants having a completion certificate showing their completion of a given program.
• Narrowing the calendar display for the program activities feature to show only calendars for the programs with which participants and facilitators are associated.
• Submitting an assessment should mark the assessment as 'complete'.

Added along the way:

• Updates for any dependent packages.
• Updates to the base Docker images used in the project.
• Any code necessary to support the above.

Screenshots

Assessments List: Participant

Assessment Detail: Participant

Assessment Submissions: Participant

Assessments List: Facilitator

Assessment Submissions: Facilitator

Checklist

• Related issue appears at beginning of pull request title with pound sign, and title describes the changes being proposed.
• Related issue is linked in pull request description using closing keywords.
• The appropriate label has been chosen for this pull request.
• The correct project has been selected for this pull request.
• All commits in this branch, including merge commits, begin with the issue number and a pound sign.
• Tests have been added, where appropriate; or, no tests are relevant for this pull request.
• This pull request contains UI changes, and screenshots of those UI images appear below; or, this pull request contains no UI changes.

[mgasquez]

Good morning, I tested all new features and they worked on the expected behavior. I would like to add that all pages look very nice and I want to say congratulations to all of us (Cohort 5 - Binary Bandits) for the great team job and excellent results.

[daveytech]

While this is an adequate feat of strength of a feature in a short amount of time, there are some design practices that would alter the system too much. Naming conventions should be revisited and old files should not be rewritten to suit newly chosen vocabulary. The changes and extension to the database have also created slight redundancies that have contributed to some unnecessary denormalization. I'd like to propose to the group and anyone willing to work on this feature, how could it be simplified/refactored and not dramatically re-written? (Just think, what if this database model affected 100+ features? Would you have made these same decisions? Try to think at a scalable level by asking questions like that.

Overall VERY IMPRESSIVE THOUGH!!!! I understand the time and resource constraints of the program can delay certain learnings and as an open-source free mentorship program we are also learning how to work with these limitations.

I'm available to discuss any design decisions with anyone who worked on this feature.