- Allow image, pdf-image, or custom file types
- Global black list extensions to prevent unsafe file types
- Custom file upload is white listed only

# Conflicts:
#	AUTHORS
#	openassessment/templates/openassessmentblock/edit/oa_edit.html
#	openassessment/xblock/static/js/openassessment-lms.min.js
#	openassessment/xblock/static/js/openassessment-studio.min.js
#	openassessment/xblock/static/js/spec/lms/oa_response.js
#	openassessment/xblock/static/js/src/lms/oa_base.js
#	openassessment/xblock/static/js/src/lms/oa_response.js
#	openassessment/xblock/static/js/src/oa_server.js
#	openassessment/xblock/static/js/src/studio/oa_edit.js
#	openassessment/xblock/static/js/src/studio/oa_edit_settings.js
#	test/acceptance/tests.py

TNL-708

TNL-708

TNL-708

Currently, Latex rendering is only supported for question prompts in ORA2. This
commit introduces Latex rendering in ORA2 student response, peer assessment
view, self assessment view, grade view, and staff-info view. The reason that
this Latex rendering code is inserted directly into ORA2 is that edx-platform,
does not know when to start Latex rendering for ORA2 views that come in via
AJAX.

This commit introduces "Preview in Latex" feature which allows students to see
their response rendered in MathJax before submission.

Conflicts:
	openassessment/xblock/static/js/openassessment-lms.min.js
	openassessment/xblock/static/js/openassessment-studio.min.js

Previously, instructors were unable to edit the feedback prompt text ("I noticed that
this response...") displayed in the response box asking a student to provide feedback
on the peer responses they received.

To allow instructors to edit this, I've added an editable xml element (feedback_default_text).
The text within the element defaults to "I noticed that this response...," but an instructor
can change this text to whatever he or she wants by editing the text within the xml element.

Editing of this new element has also been added to the authoring gui.

Fixed ORA-781, verifies passing the label-corrected context to training examples and training-example-template in addition to the rubric.

Point setup instructions to the README

Add instructions for combining/minifying static assets

Update workflow overview architecture docs

Update AI grading architecture docs

Use napoleon keyword argument instead of kwargs

Fix example usage docstrings in AI API

Conflicts:
	openassessment/xblock/static/js/openassessment-studio.min.js

Update container JS to retrieve both name and label for criteria and options

Update schema to make 'name' optional and 'label' required; the XBlock editor handler assigns UUIDs to criteria and options that don't have names

Assign labels to criteria/options if they do not have any

Update the grade template to display criteria/option labels if they're provided, otherwise use the 'name' field

Update student facing rubric templates to display the label if it's available

Add label field to XML problem definition.

Add label field to assessment

Add label field to the data dump script.

Update the turbo mode template to use option labels

Exclude the "name" key for new criteria and options in the JSON dict sent to the server.
Default new option points to 1 instead of NaN

Add data migration to fill in labels with default values

Included:
- HTML Templating using current problem defininition
- Styles
Not included:
- JavaScript changes
- Python test cleanup

Use resolve dates for default date values

Minify CSS.

Use text inputs for dates
Make feedback prompt mandatory

Remove unused debugger statements
Cleanup of JavaScript docstrings and semicolons
Sets to lists; remove errors for extraneous keys
Handle unicode correctly; fix test cases
Use .parent() instead of wrapping the HTML with <li>
Fix formatting of missing key error message
Remove extra key check
Fix feedback checkbox selector in JS
Fix rubric dict being stored in the rubric criteria list XBlock field error

Ready For Code Review.  Some things still remain to be done, but they are all stylistic Front end things:
- Styles
- Styles
- Styles
- Radio Button Inheritance on deletion
- Feedback prompt followthrough
- Comprehensive front end testing

Move openassessment out of the apps directory
Use pkg_resources to check whether OA XBlock is installed.

Studio save errors display in the UI.

Validate assessments are specified in the order: peer, then self.
Update XBlock date fields to use scope.settings and be named "start" / "due"
Add validation to workbench scenario parsing.
Resolve unspecified dates.
Use resolved dates to determine whether problem/submission/assessments are open or closed.