Potential fix for flaky TeamDiscussionView js tests

After being able to reproduce the errors exactly by making certain
elements unfindable, I concluded that the issues we've been seeing
on headless jenkins runs are due to execution happening too quickly
and elements not loading in time to be interacted with.

The fix is to make liberal use of Jasmine 1.3 `runs` and `waitsFor`
functionality, to ensure that execution happens in the order that
we want, with rendering being checked before proceeding.

Once again, I can't be 100% sure that this fixes the Jenkins errors,
as those are very hard to reliably reproduce, but this is an
educated guess at fixing the problem with no drawbacks, as I've
been able to successfully run all tests locally.

(SOL-1040) Indexing capa problems

display course id instead of name in course name placeholder, if ajax…

add ability to return the course name (optionally) when querying abou…

add ability to return the course name (optionally) when querying about credit requirement fulfillments

Remove unnecessary New Relic trace.

Switch TestRecommender to use SharedModuleStoreTestCase

Merge pull request #9394 from edx/ahsan/ECOM-2026-Credit-email-should-use-correct-staticfiles-library

Credit eligibility email should use the correct staticfiles library

Updated Certificate's config page help

Remove django-followit and django-keyedcache

Revert "JS Flakiness in TeamDiscussionView"

Upgrade django-extensions to 1.5.5

Upgrade django-ipware to 1.1.0

Update translations (autogenerated message)

ECOM-2026

Update edx-proctoring version to 0.7.1

Update edx-ora2 to release-2015-08-19T17.17.

JS Flakiness in TeamDiscussionView

Fix course info sidebar padding 

Adding waitsFor check in the beforeEach method. The condition I'm
waiting for here is shamelessly borrowed from bok-choy's
wait_for_ajax._is_ajax_finished() method:
https://github.com/edx/bok-choy/blob/master/bok_choy/page_object.py#L431

This seems to fix the errors I was able to generate with the
set_timeout, which themselves looked ver similar to the failing
master tests, so I *think* this will fix our woes, but since I was
never able to get the tests to fail exactly the same way I can't be sure.

Since there don't seem to be any drawbacks, this is going into mainline
as-is and we'll monitor for the sporadic failures over the next few
weeks.

alter columns in proctoring exam report

Fixing issue for french language

Upgrade django-babel-underscore to 0.3.0

Adds a comment to reduce confusion over remaining role name differences

Upgrade django-cors-headers to 1.1.0

Peter fogg/fix tnl 3101 quality