* Reenabling this since the renames on the schedules table are completed

* Reverting regex change that caused migration to be generated for userprofile

* Remove start field in Schedules

Co-authored-by: hunytalk <ahannan@edx.org>
Co-authored-by: Cory Lee <cory@edx.org>

This reverts commit e6f58b6d.

This is our third (3rd!) attempt to deploy stage 2 of this column rename.

* Revert "Ran make migration on third_party_auth (#23253)"

This reverts commit 49be65cc.

* Removing provider.util import

* Removing further provider things

* Adding hash tests

This reverts commit 49be65cc.

* Ran make migration on third_party_auth and removing skip comment from test_migrations_are_in_sync

* Remove ThirdPartyAuthProviderApiPermission

Also removed ProviderApiPermissions and ApiPermissionsAdminForm and removal of DOP for third_party_auth

* Removing model

* Replaced long_token with default_token_generator

* Adding skip to test_migrations_are_in_sync

This reverts commit b85aa4b3.

This stage does the following:

- Includes a data migration to copy the values from old to new field.
- Changes business logic to switch to using new field.
- Deletes all code references of the old field.

This is step 3 of DE-1824.

Also update:
* six 1.13.0 => 1.14.0
* edx-django-utils 2.0.2 => 2.0.3
* skip test that checks all model changes have migrations.  (We defer
  this to step 4.)

Enabling migration test.

Due to some recent schema changes this test is failing. Temporarily skipping it. Fix it in other PR.

This stage does the following:

- Includes a migration to delete the old column.
- NO code changes.

This stage does the following:

- Includes a data migration to copy the values from old to new field.
- Changes business logic to switch to using new field.
- Deletes all code references of the old field.

This will remove imports from __future__ that are no longer needed.

https://docs.python.org/3.5/library/2to3.html#2to3fixer-future

https://docs.python.org/3.5/library/2to3.html#2to3fixer-asserts

* ENT-2310, ENT-1289 | Running make upgrade to bump edx-enterprise to 2.0.0 (and 1.11.0)

* Skipping db_migration test for first part of removal of enterprisecustomerentitlements

Push notifications was only ever setup to connect to Parse.com a service
that has been discontinued.  Since we haven't replaced the functionality
for a few years now, remove this dead code.

In cms/templates/js/course_info_update.underscore we're allowing content
to not be escaped because this is by design according to the tests.
Long term there should be a better fix for this but for now this is
intended behavior.

https://github.com/edx/edx-enterprise/compare/0.67.0...0.67.1

https://github.com/edx/edx-enterprise/compare/0.66.1...0.67.0