feat: New header in course unit page [FC-0114]

[ChrisChV]

Description

• ENABLE_UNIT_PAGE_NEW_DESIGN flag created
• New Status Bard implemented in the header of the course unit page.
• New buttons added in the header of the course unit page.
• Which user roles will this change impact? "Course Author".

Supporting information

• Github issue: Unit Page: Header Update #2634
• Internal ticket: FAL-4301

Testing instructions

• Create a new course
• Create a new unit.
• Verify the unpublished and Upcoming states.
• Open the unit settings and check the Hide from learners and Enable discussion check. Verify that the labels for both appear in the status bar.
• Open the unit settings and add some groups in the Restrict access to section. Verify that the group names appear in the status bar.
• Publish the unit. Verify that the publish status is Published.
• Make changes in the unit. Verify that the publish status is Draft changes.
• Return to the course and set a start date before today.
• Return to the published unit and verify that the visibility state is Ready.
• Return to the course and set a start date after today.
• Return to the published unit and verify that the visibility state is Live.

Other information

N/A

Best Practices Checklist

We're trying to move away from some deprecated patterns in this codebase. Please
check if your PR meets these recommendations before asking for a review:

• Any new files are using TypeScript (.ts, .tsx).
• Avoid propTypes and defaultProps in any new or modified code.
• Tests should use the helpers in src/testUtils.tsx (specifically initializeMocks)
• Do not add new fields to the Redux state/store. Use React Context to share state among multiple components.
• Use React Query to load data from REST APIs. See any apiHooks.ts in this repo for examples.
• All new i18n messages in messages.ts files have a description for translators to use.
• Avoid using ../ in import paths. To import from parent folders, use @src, e.g. import { initializeMocks } from '@src/testUtils'; instead of from '../../../../testUtils'

[openedx-webhooks]

Thanks for the pull request, @ChrisChV!

This repository is currently maintained by @bradenmacdonald.

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.

[codecov]

Codecov Report

❌ Patch coverage is 97.61905% with 2 lines in your changes missing coverage. Please review.
✅ Project coverage is 94.90%. Comparing base (b7dd670) to head (dc68383).
⚠️ Report is 3 commits behind head on master.

Files with missing lines	Patch %	Lines
...urse-unit/header-navigations/HeaderNavigations.tsx	90.00%	2 Missing ⚠️

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #2751   +/-   ##
=======================================
  Coverage   94.90%   94.90%           
=======================================
  Files        1235     1235           
  Lines       28260    28333   +73     
  Branches     6433     6449   +16     
=======================================
+ Hits        26819    26890   +71     
- Misses       1370     1372    +2     
  Partials       71       71           

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

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.