fix: Multi Select course/course run issue

[skumargupta83]

https://2u-internal.atlassian.net/browse/CATALOG-44

Unable to Enter Course and Org Data- Discovery

Description

A recent update in the Discovery is preventing users from entering information in the Courses and Authoring Organization fields. This is impacting high-priority program operations, specifically for Google Cloud initiatives that require quick turnaround. The affected user reported being unable to input necessary data in these fields and requests an urgent resolution to restore data entry capabilities

Acceptance Criteria :

The Courses and Authoring Organization fields must allow data entry without errors for all users.
No existing programs or scheduled launches should be disrupted during the patch or rollback.

[skumargupta83]

@UsamaSadiq @openedx/committers-course-discovery could anyone please check and help review/merge this PR

[skumargupta83]

@UsamaSadiq @openedx/committers-course-discovery could anyone please check and help review/merge this PR

[UsamaSadiq]

@skumargupta83 Could you link further details on the PR about the functionality that broke this for users? Also what specific admin form/model is having the multi-select issue?
Can there be another solution based on already bundled packages instead of relying on cloudflare dns to fetch dependency on run time?

[skumargupta83]

Hi @UsamaSadiq,
I have already provided all the details in the description. If you need any clarification, please let me know a convenient time to connect. I will also explore another solution and update you accordingly.

[skumargupta83]

@UsamaSadiq @openedx/committers-course-discovery could anyone please check and help review/merge this PR

[UsamaSadiq]

Before Django 5.2 Upgrade, the courses list in studio was formatting courses as individual elements but this started failing after Django 5.2 upgrade.
This PR is a temporary fix to unblock 2U (according to @skumargupta83 from Sonata team, 2U is using course-discovery master so they need this changed merged for their pipeline to be unblocked) which can be removed/updated later on.

Current version on Django 5.2

Updated version after this fix (similar to Django 4.2 behavior)

[UsamaSadiq]

Merging this as a hot-fix for now but this needs more investigation for a proper fix and reason on why this started failing with Django 5.2 and was working fine on Django 4.2