82 multiple choice questions

[dvcabiya]

Proposed changes

---

Had to branch this off of #236 since I couldn't make questions without that modal, so approve that one first.

Created a list item that can be used to map assignment problems to HTML to represent them. Switches based on type stored in metadata, showing MCQ/Text, and put it on submission and edit pages. Right now the modal is hard locked to 5 options, but revising that would be quick. Additionally, you either receive all the points for answering a question or none at all, and if we want to introduce partial credit that would need to be updated.
Extraneous:

• Made disabled buttons have lower opacity and show not-allowed cursor on disabled
• Revised page padding for new footer placement
• Added prop to modals that greys out button unless function returns true, which can be customized to make modal not submittable if certain fields aren't filled in.

Types of changes

---

What types of changes does your code introduce?
Put an x in the boxes that apply

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation Update (if none of the other choices apply)

Checklist

---

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of
them, don't hesitate to ask. This is simply a reminder of what we are going to look for before merging your code.

• My changeset covers only what is described above (no extraneous changes)
• Lint and unit tests pass locally with my changes
• I have added tests that prove my fix is effective or that my feature works
• I have added necessary documentation (if appropriate)

Further comments

---

If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you
did and what alternatives you considered, etc...