Add fields to threads returned by Discussion API thread list endpoint

LMS/Studio: Remove Manual Sass/CSS extend files - Take 2

Addressing RTL inconsistencies on Verification process

Adds preferences API and updates users to V1 - fix

This commit adds fields that are related to the requesting user's
interaction with the thread (e.g. following).

make edxnotes bok-choy tests chrome-friendly

This eliminates some flakiness related to the loading of the notes page. It also
sets the 'no content' version of that page as a separate page object so testing
that case is more explicit.

TE-849

Revert "Adds preferences API and updates users to V1"

Customize the transaction name sent to New Relic for XBlock handlers.

Adds preferences API and updates users to V1

[LTI Provider] Adding signals for scoring events

Update ease to 0.1.3

Add CCX/IDDE configuration to yaml_config.py

Currently, all XBlock/XModule handlers are lumped together in the
same transaction (courseware.module_render:handle_xblock_callback).
This makes it difficult to pinpoint problems with specific handlers.
With this change, the transaction name will now look like:

  OpenAssessmentBlockWithMixins.save_submission
  CapaDescriptorWithMixins.xmodule_handler/problem_show

Updates to the verify student Django admin.

Merge release to master

Clytwynec/split lms unittests into shards

Update translations (autogenerated message)

Update to the latest version of celery, and django-celery.

Ensure cohort management section has loaded.

* Ensure that VerificationStatus is append-only and immutable.
* Allow searching by student for verification status.
* Properly pluralize verification status.
* Use ConfigModelAdmin for ICRV config model admin.

Move location identifying strings into index (SOL-833)

Update in-course reverification XBlock SHA in requirements.

Conflicts:
	common/test/acceptance/tests/video/test_video_times.py

Update django-debug-toolbar-mongo to work with DJDT 1.x

TNL-2120, TE-849

The parent .cohort-management class was loading faster than its children (which makes sense). However,
flakiness existed on these tests because browser actions were depending on child elements that had not
painted yet.

Tested this using chrome with no X11 forwarding for extra speed. That exposed the ajax call
as well as the sub-class rendering issues.