MICROBA-1373

Django3 has removed python_2_unicode_compatible.

Django3 has removed python_2_unicode_compatible.

Execute the codemodes on this file and removed all usage.

Execute the codemodes on this file and removed all usage.

Execute the codemodes on this file and removed all usage.

Execute the codemodes on this file and removed all usage.

Execute the codemodes on this file and removed all usage.

Execute the codemodes on this file and removed all usage.

Execute the codemodes on this file and removed all usage.

Execute the codemodes on this file and removed all usage.

fix:link fix for the yellowdig general documentation

MICROBA-1227

feat: add problem scores to progress tab api (AA-875)

This change adds three new filters to the threads API. They are:
* Filtering only threads that are flagged for abuse
* Filtering by the thread type (discussion or question)
* Filtering by the thread author

In addition it also adds a new ``abuse_flagged_count`` field for threads. It
returns a count of the number of comments in a thread that are flagged for abuse.
This is only visible to users that have moderator privileges or higher.

Finally it also adds a ``abuse_flagged_any_user`` field that is set if any user
has flagged a thread. This field too, is only visible to moderators or above.

Co-authored-by: Kshitij Sobti <kshitij@opencraft.com>

Basic prototype for self paced due dates in Studio Debugged (AA-844)

fix: fix the way that page_size is passed as a param to the enterprise catalog get_content_metadat endpoint.
edx-enterprise==3.26.23

commits
=======
- fix: change buttons in wiki modal to anchor tags

refactor: Remove use of CourseOverview model directly in the Certificates app

Also cleaned username for Authn MFE while registering using SSO/SAML.

VAN-483

and CourseSectionSequence to ensure that cascading deletes will occur to delete
the relation upon deletion of a foreign-keyed object.

This commit is phase 3 of 4 in order to ensure a smooth deploy. The phases:
1) Add separate through models for user partition groups, add fields to point to the
   separate models, and start writing to those fields as well. (COMPLETE)
2) After all models have been re-generated, switch code over to use separate through
   model fields backed by the separate through models *and* stop writing to the original
   ManyToManyField field. (COMPLETE)
3) After phase 2 is deployed smoothly, remove the original ManyToManyField fields. (This PR!)
4) After phase 3 is deployed smoothly, rename the new fields to have the same name
   as the old fields, so new_user_partition_groups -> user_partition_groups.

This PR is designed to be able to easily be rolled-back if anything goes wrong.

fix: Remove disabled v1 course certificate task code, as this was previously globally disabled (#28158)

MICROBA-1227 DEPR-155

[MICROBA-1289]
* Remove use of the CourseOverview model directly in the Certificates app
* Introduce a few new Python API functions in the `course_overview` and `catalog` django apps to replace functionality in the Certificates app.

We were generating cookie name for only stage and prod, the script
was raising an error on the Edge environment.

VAN-659

MICROBA-1380

Revert "feat: edx-enterprise==3.26.22 | set the EnterpriseCatalogApiClient get_content_metadata request page_size parameter to 50;"

This reverts commit 7eb65129.

refactor!: remove the `get_course_overview` function in favor of `get_course_overview_or_none`

feat: edx-enterprise==3.26.22 | set the EnterpriseCatalogApiClient get_content_metadata request page_size parameter to 50;
The enterprise-catalog service has a default page_size of 10.
This change means that we'll make a smaller overall number of SELECTs against the enterprise-catalog database.

Several of our cookies are meant to be shared between the LMS
and the marketing site. The previous assumption was that
SESSION_COOKIE_DOMAIN would cover both. We would like to make
it so that these can be set independently of each other.

https://openedx.atlassian.net/browse/ARCHBOM-1831

MICROBA-1227

and CourseSectionSequence to ensure that cascading deletes will occur to delete
the relation upon deletion of a foreign-keyed object.

This commit is phase 2 of 3 in order to ensure a smooth deploy. The phases:
1) Add separate through models for user partition groups, add fields to point to the
   separate models, and start writing to those fields as well. (COMPLETE)
2) After all models have been re-generated, switch code over to use separate through
   model fields backed by the separate through models *and* stop writing to the original
   ManyToManyField field. (This PR!)
3) After phase 2 is deployed smoothly, remove the original ManyToManyField fields
   and rename the new fields to have the same name as the old fields.

This PR is designed to be able to easily be rolled-back if anything goes wrong.