Use a different pytest contexts flag name to not conflict with the in…

BOM-78

BOM-70

Update uuid4().hex.decode(ascii) calls

Remove publishing for access control experimnent for now

Upgrade bulk-grades

EDUCATOR-4543 | Add utility functions to the catalog module that picks out all of the course_runs associated with a program, even those that live inside the curriculum of a sub-program.  Use these functions to populate the course -> program index of the catalog/programs cache.  Also some refactoring of a program_enrollments overview endpoint.

Upload the coverage report from reports/${TEST_SUITE}.coverage

Switch courseware.masquerade_as_student over to using a StaffAccessRu…

BOM-67 Updated the dependencies for Django-Oauth-plus

Fix course:org link creation upon rerun.

Upon rerun creation from publisher course:organization link
was not creating, due to which org logo was not appearing on
course certificates.

Fixed by creating course:org link upon rerun.

PROD-125

-Removed Submit-feedback View
-Removed related tests
-Removed help_modal.html
-Removed help_modal.html test
-Removed zendesk from requirements
-Updated requirements

added the updated dependency for oauth2

added the commit hash instead of branch

minor fix

changes made by make upgrade

Upgrade moto to support python3.

Test the django admin view, and that it can be loaded

Since we want anonymous read of these objects, we have to be explicit about
the bucket permissions or the test will fail.

Moto has a vendored version of HTTPretty which also monkey patches the
socket object.  If you activate both, you get weird errors like
https://github.com/spulec/moto/issues/750

So we're opting not to activate both in this test.  We're are just using
the moto vendored version of httpretty for both our usage and the
mocking of boto.

I also removed the logic that seemed like it was just testing that our
mock is a mocking s3 correctly.

They are running into issues because of a bug in moto but looking closer
at what they are testing.  Both tests test the happy path of the
underlying function.  In the happy path scenario all boto calls succeed
and all theses test do is test that but with all the boto calls mocked
out.  So we're just testing whether the mock is a good mock of boto
which is not useful.

Longer term we should move to boto3 in general and then we can use the
default moto mock for s3.

We had to pin json diff because of how we pull prod requirements into
testing.txt

SE-1199 Campus.il Fix unicode username hints with SSO

SE-1155 [Campus.il] fix crashes on non-ascii in usernames for ccx enrollments

* Add optional role parameter to course API endpoint.

* fixup! Add optional role parameter to course API endpoint.

edx-platform version bump

DEPR-15: Remove usage of firebase-token-generator

Update Help msgs of management commands

PROD-399

INCR-405 python3 compatibility