Remove DOP apps from INSTALLED_APPS.
Remove DOP libraries from requirements.

the patched toggle was removed from edx-drf-extensions recently

DENG-17 Dropping the FK on schedulesexperience->schedule to apply change to schedule as a gh-ost migration (#23242)

Feanil/remove unvaluable bokchoy tests

BOM-1324: remove oauth2.enforce_jwt_scopes toggle

* Removing from provider imports from openedx

 * removed all uses of retire_dop_oauth2_models

* Removing provider library from lms, common, and cms

Created/copied function short_token(from django-oauth-provider) and create_hash256 to help with conversion

The last time we tried this upgrade we encountered timeouts on the quality job, which it now appears were due to the worker running pylint common running out of memory and killing the Jenkins process. Switching to a different worker type with double the RAM (8 GB vs. 4 GB) seems to have fixed this; about 5.5 GB was used. Upstream is aware of the high memory usage on large projects, it's apparently due primarily to a cache of parsed modules: https://github.com/PyCQA/pylint/issues/1495 .

Even after disabling some of the new checks that have been added, the new version of pylint found about twice as much to complain about. Just bumping the threshold for now to unblock the Django upgrade, we can try automated utilities like pyupgrade to fix some of these later.

Fix Deprecation: log.warn -> log.warning

Add url_slug to the CourseOverviewTab, to support serializing StaticTabs

Revert "BOM-1069"

TNL-7093 Use inline styles to reset display to block from table-cell and width to auto

This reverts commit 140738df.

BOM-1069

-django-babel-underscore custom version to support django>=2.2

Video Bumper feature is not valuable enough to keep UI tests for.

This feature has been un-used for years and doesn't merit having
expensive UI tests.

Reruns are created by the API and we don't care about the UI as much.

Test the crucial UI features only.

This feature is not valuable enough to warrant an expensive UI test.

We don't use this UI for creating courses anymore.  This is done
via publisher.  So while the underlying APIs need to work. The UI
is not as valuable to test.

These tests are not worth the amout of time we're spending on them
because the things they are testing are not high value.

Not critical enough to keep as a part of bokchoy.

The batch feature is unlikely to change and hits a tested backend API.
The EntranceExam is not a sufficiently highly used test to warrante the
expense of UI tests.

This feature is not sufficiently important to warrant expensive UI tests.