fix: bring back email_marketing model momentarily and bump enterprise

* prevent a backbone fieldview race condition that can delete user input

eslint for effected

* Fixing quality

* Allow _super in fields.js

* Fixing new issues

* Revert some changes

* Fixing errors, formatting

* Fix bug

* Fix eslint rule allowing _super

* Refactor code

Co-authored-by: Dylan Grafmyre <dylan@opencraft.com>
Co-authored-by: Paulo Viadanna <paulo@opencraft.com>

Enterprise was still using email_marketing code. This will bump
enterprise to a version that does not any more. And also temporarily
put the email_marketing model back for blue/green deploy sanity.

ENT-4392: Updated edx-enterprise version

feat: drop unused EmailMarketingConfiguration model

docs: ADR for exposing existing studio views through new JWT-enabled endpoints [BD-03] [BB-3965]  (#27129)

* docs: ADR for exposing existing studio views through new JWT-enabled endpoints

To allow MFEs to drive existing studio functionality, we need to expose that
functionality via REST APIs that can be used by MFEs. This ADR describes an
approach to do that.

* Update cms/djangoapps/contentstore/docs/decisions/0002-restful-studio-apis-for-MFE.rst

Co-authored-by: Farhaan Bukhsh <farhaan@opencraft.com>

* Update cms/djangoapps/contentstore/docs/decisions/0002-restful-studio-apis-for-MFE.rst

Co-authored-by: Kyle McCormick <kdmc@pm.me>

Co-authored-by: Farhaan Bukhsh <farhaan@opencraft.com>
Co-authored-by: Kyle McCormick <kdmc@pm.me>

feat: add code_owner_squad custom attribute

This follows on the commit that gutted the email_marketing djangoapp
by actually dropping the model from code and database.

The djangoapp could now be removed after Maple releases.

AA-607

feat!: remove all email_marketing djangoapp code

Upgrade edx-django-utils to bring in the new
code_owner_squad custom attribute for
monitoring purposes. See the edx-django-utils
changelog for details.

ARCHBOM-1551

This djangoapp was designed for talking to sailthru, in a fairly
edx.org-specific way. Nowadays, edx.org doesn't need this code and
if other installations do, it's better off as a more distinct
plugin anyway, rather than direct support in the platform.

I've moved the one signal that was still useful (calling
segment.identify() whenever user fields change) into user_authn.

And I've left the EmailMarketingConfiguration model alone for now,
but will remove that shortly. Nothing uses it as of this commit.

AA-607
DEPR-139

MST-698 Remove escaping for Proctoring Requirements email on course_name and proctoring backend name (#27500)

The course name can contain apostrophes and other special characters. The email template right now escapes every words. This is not desired because it can render apostrophes like #39;. Update the email templates so only second half of the email template is escaped

fix: include VerifiedModeSerializerMixin in Progress Tab API [AA-723]

MICROBA-1021

fix: properly set contains_gated_content field on xblocks again

MICROBA-1013

This has been broken for a couple months, preventing proper display
of verified-only assignments on the dates tab and elsewhere.

AA-780

DEPR-140 MICROBA-985

MICROBA-1013

If a certificate available date was set on a self paced course, it would
show text to the learner saying that the grades would be available in
the future when that was inaccurate.

* fix: pin python-slugify<5.0.0
transifex-client requires python-slugify<5.0.0 for Python 2.0 support which conflicts with the latest python-slugify version.

[VAN-437] - Unlocking the learners upon successful password reset

* Commits:
  docs: Remove completed TODO discussions item
  feat: Add support to Discussions API for legacy cohort settings
  refactor: Remove get_course_discussion_settings helper
  refactor: Remove set_course_discussion_settings helper
  refactor: Add better DRF support to legacy discussions settings

fix: Add callback function to Facebook share

so that we can re-use the existing serializer as a portability-shim in
the new API.