changes made to fix jenkins/quality errors

changes made as suggested

added the docstring to fix quality issue

made a few changes to fix some tests

replaced json.loads with a util to handle bytes

changes made to fix jenkins/quality errors

changes made as suggested

added the docstring to fix quality issue

made a few changes to fix some tests

made changes as suggested

made changes as suggested

updated the requirements with make upgrade

Fixed all instances of "TypeError: a bytes-like object is required, not 'str" - BOM-914

Regisb/simplify swagger auto schema

We'd like to add this status to help distinguish between learners
who've graduated from the program and learners who warranted some sort
of removal from the program.

JIRA:EDUCATOR-4702

Python Requirements Update

ENT-1688: Changed logout message on on logout screen for Enterprise SSO flow

remove mailchimp tracking

Changes to show blank screen instead of logout message for Enterprise SSO flow. It confuses learner when they are already signed in and access their course from B2B site.
ENT-1688

Fixed pep8 quality violation

use testserver as HOST instead of edx.org

assert enterprise app is enabled

added logging

Print different values

Reload django url config

assert all quote operations to see how they work on jenkins

debug url resolved values

login user in setup

added log to debug test on jenkins

Using UrlResetMixin

Using regex instead of resolve

Fixed quality violation

Fixed pylint quality violations

Fixed target interpolation syntax

Added developer's comment

ENT-2384: Invoke learner transmission task only for enterprise learners

Fixed - " AttributeError: 'str' object has no attribute 'decode' " - BOM-922

Invoke learner transmission task only for enterprise learners
ENT-2384

added docstring

Fixed brokent unit test

BOM-925

BOM Project Xblock Recommber integration tests fix

Fixing TypeError, the JSON object must be str, not 'bytes'.

BOM-924

Fixing TypeError, the JSON object must be str, not 'bytes'.

changes made to pass tests with python 2 and other minor changes

Updated the tests to fix the string/bytes input

changes made to pass tests with python 2 and other minor changes

made some changes as suggested

made changes as suggested

changes made as suggested

Python3 json can not work with bytes type input so used simplejson
instead of python json which works with both bytes and unicode
type input.
Previously we mistakenly updated StringIO to six.String io. which
caused the tests failure. Used io.BytesIO to fix the issues as
assci character bytes can not be converted to unicode.

BOM fix remaining capa module issues

Removed encode method to fix input to csv write method - BOM-837

BOM-805

removed unnecessary encode method to fix input to csv write method

python3 compatibility: Before comparison with unicode decode text if its type is bytes.

BOM-898 fix test_responsetypes.py issues
Updated safe_exec to use random2 library instead of random.
As python3 random generates different results as compared to
python2, which causes a lot of test failures and if we use
python3 random and fix tests it will cause state invalidation
of capa problems, So random2 was uses to make the behaviour same
in python3.

BOM-899 name xrange is not defined
xrange is used in safe_exec and there might be old courses where
this is being used in capa problems. All those tests fail in python3
as this was renamed to range. Used six.moves.xrange so that code
works for python3 and if there is any old code using xrange it
works too.

BOM-804

Updated the items order in response list comparison to work with both python versions - BOM-819

The API documentation decorators do not have to leak which solution we
use to generate the docs. Here, and as discussed in PR #21820, we rename
the `openapi` module to `apidocs`, and we make sure that this module
includes all the right functions to document API Views without referring
to Open API.

Instead of relying on a `method_decorator`, we explicitely declare the
`get` method.

The `swagger_auto_schema` view function decorator allows us to
auto-document API endpoints. All swagger arguments are passed as kwargs
to the decorator, but this feels a bit unnatural: we would like to use
the function documentation as the endpoint summary and description. We
introduce this feature here by reading the `__doc_`_attribute of the
view function.

BOM-917

BOM-916