feat: Add "Recently Modified" library section [FC-0059]

[yusuf-musleh]

Description

This PR adds the "Recently Modified" section in the Library Home Page along with the "View All" button that appears in other sections if there is more content than what is previewed.

Recently Modified Section
This section shows the most recently modified/created 4 or less library components. If there are no components yet in the library the section will not appear on the page. This section will always show those components regardless of whatever search terms or filters have been applied.

View All button
The "View All" button appears on all sections in the library page (excluding the "Recently Modified" section) when the number of content in the section exceeds what is being previewed (currently that limit is 4). Clicking on the "View All" button should navigate to the sections Tab to view all the content, while maintaining any search terms/filters/sorting applied.

Supporting information

Related Tickets:

• Library Search Home Tab - Recent and Components #1039
• Depends on feat: adds sortable fields to studio content search index [FC-0059]  edx-platform#35103

Testing instructions

1. Make sure you have edx-platform running locally
2. Run this branch locally
3. Make sure you have a few libraries created (you can use the soon-to-be-deprecated library-authoring mfe):
   1. A library that has 0 components
   2. A library that has more than 4 components
4. After creating/updating the libraries, make sure to run ./manage.py cms reindex_studio --experimental in the cms container to update the search indexes with latest data
5. In the course-authoring mfe, navigate to the libraries tab
6. Click on the library that has 0 components:
   1. Confirm that the it shows the empty state, and no "Recently Modified" section
7. Click on the library that has more than 4 components:
   1. Confirm that the "Recently Modified" section is shown in the home tab
   2. Confirm that the components show are in fact the most recently modified
   3. Confirm that performing a search/filtering/sorting has no impact on that section
   4. Confirm that the "View All" button is shown in the components section when there are more than 4 results
   5. Confirm that clicking on the "View All" button navigates to the "Components" tab, while maintaining any sorting/filtering/search terms applied
   6. Perform a filter or search to get 4 or less results, and confirm that the "View All" button is no longer displayed and that the number inside the components is updated to reflect how many components match
8. Confirm that the modifying a component in the library (using the library-authoring mfe or shell) and updating the search index (see cms command above) will include that component at the beginning of the "Recently Modified" section.

---

Private-ref: FAL-3759

[openedx-webhooks]

Thanks for the pull request, @yusuf-musleh!

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.

🔘 Update the status of your PR

Your PR is currently marked as a draft. After completing the steps above, update its status by clicking "Ready for Review", or removing "WIP" from the title, as appropriate.

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

Who will review my changes?

This repository is currently maintained by @openedx/2u-tnl. 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.

[yusuf-musleh]

Tests should pass after this fix is added upstream.

[pomegranited]

👍 Works and looks great @yusuf-musleh !

One nit, and there's 2 failing tests, but this is good to go once they're fixed.

• I tested this using my tutor dev stack and the PR test instructions
• I read through the code on feat: Add "Recently Modified" library section (TEMP) open-craft/frontend-app-authoring#52
• I checked for accessibility issues by using my keyboard to navigate
• Includes documentation
• User-facing strings are extracted for translation

[pomegranited]

Merged this branch into WIP #1147, so will get this merged upstream as part of that.

[openedx-webhooks]

@yusuf-musleh Even though your pull request wasn’t merged, please take a moment to answer a two question survey so we can improve your experience in the future.