fix(hierarchy): hide parent draft text in publish confirmation [FC-0123]

[navinkarkera]

Description

Fix publish confirmation hierarchy messaging for Library Authoring sidebar.

When selected row has descendants/ancestors in hierarchy, parent rows no longer show Draft chip and parent warning text removed from confirmation copy. This avoids confusing message that parent rows "will be draft" while publishing selected item.

Impacted role: Course Author.

UI impact:

• Publish confirmation modal text now shows child warning only.
• Hierarchy status chips no longer show Draft on parent rows of selected item.

Supporting information

• Related: [Publish confirmation] Hide incorrect hierarchy diagram labels #2466
• Jira: FAL-4331

Testing instructions

1. Open Library Authoring.
2. Pick container with unpublished changes in hierarchy (section/subsection/unit).
3. Open item sidebar and click Publish Changes.
4. Verify confirmation modal shows:
   • "Confirm Publish" heading.
   • Child warning sentence only.
   • No parent warning text like "Its parent ... will be draft".
5. In hierarchy widget inside confirmation modal:
   • Selected row and descendants show Will Publish as expected.
   • Parent rows do not show Draft chip.

Best Practices Checklist

• 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, @navinkarkera!

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.46%. Comparing base (839ac71) to head (248f6ad).
⚠️ Report is 2 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #3029      +/-   ##
==========================================
- Coverage   95.47%   95.46%   -0.01%     
==========================================
  Files        1381     1381              
  Lines       32566    32554      -12     
  Branches     7472     7470       -2     
==========================================
- Hits        31091    31079      -12     
  Misses       1406     1406              
  Partials       69       69              

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

[ChrisChV]

@navinkarkera Looks good 👍

👍

• I tested this: I followed the testing instructions
• I read through the code and considered the security, stability and performance implications of the changes.
• I tested that the UI can be used with a keyboard only (tab order, keyboard controls).
• Includes tests for bugfixes and/or features added.
• Includes documentation