fix: Nits on UX/UI in the new sidebars in course outline and unit page [FC-0114]

[ChrisChV]

Description

• Fixes the open nits/issues listed in UX/UI bugs for new course outline and unit page sidebars #2868
• Fixes the small nit in the back button in the import workflow: Import from Course stepper UI #2524 (comment)
• Fixes the small nit in the unsupported text in the import workflow: Import analysis + start import button #2525 (comment). This fix depends on fix: Typo in unsupported reason message in content libraries [FC-0114] openedx-platform#38005
• Which user roles will this change impact? "Course Author".

Supporting information

• Github issues:
  • UX/UI bugs for new course outline and unit page sidebars #2868
  • Import from Course stepper UI #2524 (comment)
  • Import analysis + start import button #2525 (comment)
• Related PR: fix: Typo in unsupported reason message in content libraries [FC-0114] openedx-platform#38005
• Internal ticket: FAL-4308

Testing instructions

Sidebar issues:

• Go to a course outline
• Verify that the issues listed in UX/UI bugs for new course outline and unit page sidebars #2868 are fixed.

Issue #2524 (comment):

• Go to a content library
• In the header, go to Tools > Import.
• Start an import.
• Select a course.
• Verify the new design of the Back button.

Issue #2525 (comment):

• Use this branch of the edx-platform: fix: Typo in unsupported reason message in content libraries [FC-0114] openedx-platform#38005
• Run these commands in the cms shell to fix the old migration unsupported reasons:

# Preview the affected records
blocks = ModulestoreBlockMigration.objects.filter(unsupported_reason__contains='so it not supported')
print(blocks.count())

# Fix them
for block in blocks:
    block.unsupported_reason = block.unsupported_reason.replace('so it not supported', 'so it is not supported')
    block.save(update_fields=['unsupported_reason'])

• Create a course and a unit
• In the unit add a legacy library block.
• Go to a content library
• In the header, go to Tools > Import
• Start an import
• Select the new created course.
• Run the import
• After the import verify that the message is correct.

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.

Details

---

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 95.22%. Comparing base (d1c3fb9) to head (43cc199).
⚠️ Report is 5 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff            @@
##           master    #2871    +/-   ##
========================================
  Coverage   95.22%   95.22%            
========================================
  Files        1328     1330     +2     
  Lines       30510    30517     +7     
  Branches     6668     6904   +236     
========================================
+ Hits        29053    29060     +7     
+ Misses       1400     1388    -12     
- Partials       57       69    +12     

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

[navinkarkera]

@ChrisChV Added some suggestions and nits.

[ChrisChV]

@bradenmacdonald could you review this PR?