feat: add component Details sidebar [FC-0062]

[rpenido]

Description

This PR adds the Details tab in the Component Sidebar.

More information

Part of:

• Component Sidebar: Details Tab #1195

Depends on:

• feat: return modified date information on get component endpoint [FC-0062] edx-platform#35508

Testing Instructions

• Checkout this branch and feat: return modified date information on get component endpoint [FC-0062] edx-platform#35508
• Create a new library and add a component to it
• Click on the component and check the draft status on the Details tab
• Update the component name
• Check the updated modified date in the Component History

---

Private ref: FAL-3803

[openedx-webhooks]

Thanks for the pull request, @rpenido!

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

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 92.73%. Comparing base (9d3a05f) to head (a9a7b21).
Report is 13 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #1303      +/-   ##
==========================================
+ Coverage   92.47%   92.73%   +0.25%     
==========================================
  Files        1025     1035      +10     
  Lines       18978    19261     +283     
  Branches     4048     4079      +31     
==========================================
+ Hits        17550    17861     +311     
+ Misses       1360     1335      -25     
+ Partials       68       65       -3     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[rpenido]

Missed comment from the ComponentManagent tab test

[pomegranited]

One nit, but 👍 when that's fixed :)

• I tested this using the PR test instructions
• I read through the code
• I checked for accessibility issues by using my keyboard to navigate
• Includes documentation N/A
• User-facing strings are extracted for translation

[ChrisChV]

@rpenido Looks good 👍 One small nit, but not a blocker.

[ChrisChV]

I think we can throw an error instead of null. (ex.)

[rpenido]

Thank you @ChrisChV!
I added a better error handling here (a9a7b21), adding a loading and error state, as this could have an error from api.