feat: add publish status to library meilisearch index

[DanielVZ96]

Description

Adds the publish status field to the libraries v2 meilisearch index in order to support filtering by component publish status: published, modified, never.

Supporting information

• Issue: Add publish status filter frontend-app-authoring#1484
• Blocks: Allow filtering library by publish status [FC-0062] frontend-app-authoring#1406

Testing instructions

0. [If needed] Create a new library with new components in http://apps.local.openedx.io:2001/course-authoring/libraries
1. With the tutor stack running execute the following command: tutor dev exec cms bash -c './manage.py cms reindex_studio --experimental '
2. Navigate to http://localhost:7700/
3. Assert that the publish_status of the documents matches their respective components:
   • Published when the component was published and not modified since
   • Modified when the component has been modified after being published
   • Never when the component has never been published

Deadline

ASAP

Other information

Private-Ref

[openedx-webhooks]

Thanks for the pull request, @DanielVZ96!

What's next?

Please work through the following steps to get your changes 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.

🔘 Let us know that your PR is ready for review:

Who will review my changes?

This repository is currently maintained by @openedx/wg-maintenance-edx-platform. Tag them in a comment and let them know that your changes are ready for review.

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.

[pomegranited]

This is working great, but I'm not sure that we need it?
If we do keep it, we need one more test, so I'm happy to conditionally approve. 👍

• I tested this using the test instructions for feat: allow filtering library by publish status frontend-app-authoring#1570
• I read through the code
• I checked for accessibility issues N/A
• Includes some documentation
• User-facing strings are extracted for translation N/A

[pomegranited]

Hmm.. technically this status can be determined using filters on the existing xblock document metadata fields, so we don't strictly need a field publish_status field in the search index. e.g to filter out unpublished items when sorting by "Recently Published", we add a last_published IS NOT NULL filter.

But I'm not sure what our stance is on having too much logic living in the frontend.. @bradenmacdonald what do you think?

[pomegranited]

(If we end up keeping this field) could you please add a test for "publish_status": "modified"?