feat: [FC-86] add sorting feature for engines + enable_course_sorting_by_star…

[andrii-hantkovskyi]

Add Sorting Feature for Engines + enable_course_sorting_by_start_date Parameter

This PR introduces a sorting feature for search engines and adds a new parameter, enable_course_sorting_by_start_date, to the course discovery search.

Key changes:

• Adds enable_course_sorting_by_start_date to the course discovery search API, allowing results to be sorted by course start date when enabled.
• Implements a generic SortField dataclass and FieldTypes enum to support flexible sorting across different search engines.
• Updates ElasticSearch, Meilisearch, and mock search engine backends to support sorting via the sort_by parameter.
• Ensures Meilisearch index is configured with start as a sortable field.
• Updates the course discovery view to accept and forward the new sorting parameter.
• Adds comprehensive tests verifying sorting behavior by course start date.

These changes allow consumers to opt into sorting course results by start date, enabling richer search and browsing experiences across all supported backends.

[openedx-webhooks]

Thanks for the pull request, @andrii-hantkovskyi!

This repository is currently maintained by @Ali-Salman29.

Once you've gone through the following steps feel free to tag them in a comment and let them know that your changes are ready for engineering review.

🔘 Get product approval

If you haven't already, check this list to see if your contribution needs to go through the product review process.

• If it does, you'll need to submit a product proposal for your contribution, and have it reviewed by the Product Working Group.
  • This process (including the steps you'll need to take) is documented here.
• If it doesn't, simply proceed with the next step.

🔘 Provide context

To help your reviewers and other members of the community understand the purpose and larger context of your changes, feel free to add as much of the following information to the PR description as you can:

• Dependencies

  This PR must be merged before / after / at the same time as ...

• Blockers

  This PR is waiting for OEP-1234 to be accepted.

• Timeline information

  This PR must be merged by XX date because ...

• Partner information

  This is for a course on edx.org.

• Supporting documentation
• Relevant Open edX discussion forum threads

🔘 Get a green build

If one or more checks are failing, continue working on your changes until this is no longer the case and your build turns green.

Details

---

Where can I find more information?

If you'd like to get more details on all aspects of the review process for open source pull requests (OSPRs), check out the following resources:

• Overview of Review Process for Community Contributions
• Pull Request Status Guide
• Making changes to your pull request

When can I expect my changes to be merged?

Our goal is to get community contributions seen and reviewed as efficiently as possible.

However, the amount of time that it takes to review and merge a PR can vary significantly based on factors such as:

• The size and impact of the changes that it introduces
• The need for product review
• Maintenance status of the parent repository

💡 As a result it may take up to several weeks or months to complete a review and merge your PR.

[andrii-hantkovskyi]

Hi @diana-villalvazo-wgu would you have a chance to review this PR when you have a moment?

[ormsbee]

Just a few high-level questions to start with.

[diana-villalvazo-wgu]

LGTM

[Abdul-Muqadim-Arbisoft]

@andrii-hantkovskyi Since this PR is approved, can we go ahead and merge it? Looking forward to it.

[Serj-N]

@andrii-hantkovskyi Since this PR is approved, can we go ahead and merge it? Looking forward to it.

@Abdul-Muqadim-Arbisoft Hi! I'm stepping in for @andrii-hantkovskyi. We will have one final look at this and move forward with a merge.

[sarina]

Hi all, what's the status on this PR? It has an approval from July 21st. It's blocking work on the Catalog MFE. Can we get it merged?

[Serj-N]

Hi all, what's the status on this PR? It has an approval from July 21st. It's blocking work on the Catalog MFE. Can we get it merged?

@sarina Hi! We see no problems with this PR, so you can safely merge it.

[sarina]

I'm not a CC on this repo. @ormsbee was there a reason you didn't merge this after your approval?

[feanil]

@Ali-Salman29 can you merge and release this change?

[ormsbee]

@sarina: I didn't merge at the time because I thought the team would want to control the merge timing/rollout, and I had assumed someone on the team had access to do so. I'll just merge it now.

[feanil]

FYI, it looks like we didn't bump the verison or publish the repo so I'll do that now. #224 bumps the version.