Add logging middleware to determine why our responses are bad.

Fix serialization issues in codejail

Re-raise issue was in codejail.

Update xblock-lti-consumer with more Python 3 fixes.

- Undo the previous change.
- Pull in the version of codejail with the fix for the issue.

Ignore bad cached data.

When migrating from python 2 to 3 we can get in a situation where the
cache has data that the new version of python can't read.  In this case
drop the bad data and re-cache the correct data.

Upate xblock-lti-consumer to get more Python 3 fixes.

Redirect to the view names directly.

Use six to reraise a capa error.

Feanil/handle pickling failure

create CSM service

fix flaky test_login unit test

ARCH-1253

Upgrade edx-enterprise

Students can't create team in an instructor-managed topic

Move account_settings into user_api.

Add ENABLE_COURSEWARE_SEARCH_FOR_COURSE_STAFF flag

log exception for further context

We use pickling in conjunction with caches in these cases so we should
be able to fallback to the uncached behavior if the pickled data is
corrupt in some way.

eg. it's a python 2 pickle we don't know how to read.

When going between python 2 and python 3.5 we can get pickeld course
structires that are incompatible no matter what we do do to the bug
linked in the comment.  In this case, handle the error and delete the
corrupt data from the cache.

Making this fairly generic because if we have any bad data in cache we
don't want it to blow up the whole process.  Just delete the bad data
and try again.