EDUCATOR-11

This specifically enables/disables the underlying comment service client
used to make calls to the service.  When disabled, this client will now
throw an exception which can be propagated upwards so that callers can
make the right decision about how to notify users of the error, or
handle retry, etc etc.

More accurately, this creates a 4th shard because the
last shard is always the default.

More accurately, this creates a 4th shard because the
last shard is always the default.

* Upgrade edx-submissions
* Upgrade edx-ora2
* Upgrade edx-val
* Upgrade edx-proctoring
* Update all edx-platform code that depends on DRF, including:
  - auth_exchange
  - cors_csrf
  - embargo
  - enrollment
  - util
  - commerce
  - course_structure
  - discussion_api
  - mobile_api
  - notifier_api
  - teams
  - credit
  - profile_images
  - user_api
  - lib/api (OAuth2 and pagination)

* Upgrade edx-submissions
* Upgrade edx-ora2
* Upgrade edx-val
* Upgrade edx-proctoring
* Update all edx-platform code that depends on DRF, including:
  - auth_exchange
  - cors_csrf
  - embargo
  - enrollment
  - util
  - commerce
  - course_structure
  - discussion_api
  - mobile_api
  - notifier_api
  - teams
  - credit
  - profile_images
  - user_api
  - lib/api (OAuth2 and pagination)

refactor community_ta and staff in docstrings

MA-1212 - added response count field in tests

removed unneccessary function

"MA-1212 - added response count in thread retrieval service and updated tests"

updated serializerz test for response count

MA-1212

exclude response count from thread get list

removed response_count field from update and create thread services

made resp_total dynamic for cs thread in test_serielizer

quality fixed

improved quality

add TODO JIRA ticket on removed fields

Discusion API now takes a view parameter when getting a thread list.
This view parameter only takes "unread" or "unanswered" as possible
values.

This also fixes two bugs:
* A thread created by a non-privileged user in a cohorted course would
  not have group_id set
* Any user could set the endorsed field on creation of a comment

Flagging/unflagging is done by issuing a PATCH request on a thread or
comment endpoint with the "abuse_flagged" field set.

Add more extensive testing

This will allow clients to determine what actions (e.g. following,
endorsing, and editing content) a user can take on a piece of content.

The comments service rejects whitespace-only content for certain
strings, so the discussion API should also reject such content.

Some old threads do not have the pinned field set, which the thread
serializer should handle.

The rendering in this commit does not prevent MathJax content from being
rendered as the discussion JavaScript code does.

This is done via PATCH on a comment instance endpoint.

This depends on cs_comments_service commit 0487891.

This is done via PATCH on a thread instance endpoint.

Also, fix the field-specific error format for all API endpoints.

This requires cs_comments_service commit fdf017c918.