feat: [FC-86] Added DataTable for Catalog page

[PKulkoRaccoonGang]

Note

Filtering logic will be added in the next PRs related to the course Catalog page.

Description

This PR includes the following changes:

A Paragon DataTable component has been added to the course Catalog page to display course cards. Also added a Paragon Form.Control component that will be used for searching on this page.

Initial setup

1. Clone and install the tutor-mfe plugin from the draft PR that adds support for Catalog MFE.
2. Go to http://apps.local.openedx.io:1998/catalog/courses

How Has This Been Tested?

1. Go to Course Catalog page (http://apps.local.openedx.io:1998/catalog/courses).
2. When loading the page, a loader (spinner) is displayed.
3. If there are no courses, an alert is displayed with information about this.
4. Course cards are displayed inside the DataTable component (logic related to filtering courses will be provided later).
5. The Form.Control component is displayed correctly (search logic will be added later)
6. The page is displayed incorrectly on mobile screens.
7. If an error occurred while loading the page content - an error message is displayed (message taken from LearnerDashboard MFE).

8. Create a new course from Studio.
9. Check the display of the course card on the new Course Catalog page.
10. If there is no course image, the default image is displayed.

11. Through the Schedule and Details page, load the course image and check on the Course Catalog page that the image is displayed.
12. By clicking on the course card, the New Course About page opens (http://apps.local.openedx.io:1998/catalog/courses/<course_id>/about) without full page reloading (React Router).

Merge Checklist

• If your update includes visual changes, have they been reviewed by a designer? Send them a link to the Sandbox, if applicable.
• Is there adequate test coverage for your changes?

[openedx-webhooks]

Thanks for the pull request, @PKulkoRaccoonGang!

This repository is currently maintained by @openedx/committers-frontend.

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.

🔘 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.

---

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.

[PKulkoRaccoonGang]

Reopened at raccoongang#22