Fix the issue that was preventing us from upgrading pytest.  pytest does some manipulation of test packages that prevents `pkg_resources` from loading resources from them, but used to contain a workaround for the problem.  That workaround was [removed](https://github.com/pytest-dev/pytest/issues/5392) in 4.6.0 as a performance enhancement when pytest switched from `pkg_resources` to `importlib-metadata` for its own entrypoint handling.  This tripped up one of our test modules which defined classes that loaded templates from inside a test package.  Moving these resources to the parent package fixes the problem.

More and more, `pkg_resources` is being abandoned in favor of `importlib-metadata` and `importlib_resources` as they have a simpler design with much better performance.  However, `importlib_resources` doesn't support loading files from any directory which isn't itself a Python package (and doesn't allow direct use of paths including directories within the package).  Jinja2 chose a [different approach](https://github.com/pallets/jinja/pull/1082) that we may want to emulate in our resource handling.

Also fixed usage of a removed `pytest.raises()` parameter and a bug in our configuration of the `common/lib` tests that became a problem after the upgrade.

Specifying a namespace in django.conf.urls.include() without providing an app_name is deprecated.
Adding the app_name attribute in the included module.

* Switch make upgrade to Python 3.5

* bok-choy fixes, constrain django-debug-toolbar

* Remove flaky bok-choy test

There was a serialization issue with one of the studio JS assets that
is rendered as a part of the edit view.

-point to updated edx-organizations package

updated the tests

minor changes

changes made verify capitalized country code

changes made verify capitalized country code

changes made stay consistent with country code implementation

changes made to test with previous implementation

updated the django-countries version to latest

updated the tests input to match the output

updated the constants to use updated country names according to new ISO standards

Upgrade django-ses

-bumped django-model-utils version to support django 22

downgrade the django-cors-headers version to 2.5.3

downgrade the django-cors-headers version to 2.5.3

updated the django-cors-headers to version that supports django 2.2

downgrade the django-cors-headers version to 2.5.3

downgrade the django-cors-headers version to 2.5.3

updated the django-cors-headers to version that supports django 2.2

downgrade the django-cors-headers version to 2.5.3

downgrade the django-cors-headers version to 2.5.3

ran make upgrade

BOM-1094

Upgrade django-debug-toolbar

Microsoft social login is not working on edx mobile app. The issue
is fixed in newer version of social-auth-app-django.

PROD-718

DE-1824: step 2 of 4 in renaming 'exists' field in ThirdPartyTranscriptCredentialsState to 'has_creds' (v1.1.33)

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

This commit upgrades the version of pymongo from 2.x to 3.x, removing usages to deprecated functions usage and fixing tests where necessary.

This version of pymongo supports MongoDB 2.x all the way up to 4.2, and this ensures that the platform will be able to run on a supported MongoDB version in the next release.