This introduces a few features:
* INFO level logging on common events like creating or fetching
  submissions and assessments.
* Parallel event logging for the same.
* Creates a local logs/ directory for development.

For the most part, we rely on XBlock's publish() mechanism to emit
event data. However, because scoring is done at the API layer in a way
that is not directly visible to the OpenAssesmentBlock, we're logging
that event separately with a hacky solution that dynamically loads an
emit function based on a configuration value. This is a stopgap
measure until we can start using the edX analytics API (which is still
in testing).

TIM-260, TIM-378

Change scenario due date to be in the future and minor changes to prompt text.

Revert setup.py name change back to ora2

Preserve line breaks in prompt

Fix 500 error when self-assessment has default dates

Changing is_open to is_closed. We're negative like that.

UI Clean Up - Small Tweaks

Performance changes for staggered deadlines

This change improves the query when you have 35,000 open peer workflows and 0 assessments. Performance appears to still be good for a fluid workflow as well.

TIM-337: Feedback on assessment UI

Adding start date validation to assessment modules

Sylvia/ora2/tim 384

Acknowledge Submission Deadline

* provides static states for submission cases
* adds in abstracted system-feedback sass partial
* adds in starter animation sass partial
* syncs up loading style for steps with standards
* moves message UI archetypes/variables to the xblock level of Sass architecture

Move JS grade step into a separate file
Feedback on submission UI wiring

TIM-304

Move JavaScript response step code into separate view class.
Implement unsaved draft and save button enable/disable

Update turbo mode to only be open after submission deadline

TIM-346: Server-and-client-side size validation