chore: upgrade Authoring MFE slot IDs to namespaced version

[tecoholic]

Authoring MFE's slots were updated to use the namespaced ID format for all the slots in frontend-app-authoring PR#1854.

This commit brings the latest IDs to the Authoring MFE patch and also upgrades the unit-page sidebar slot to the latest version - v2.

[openedx-webhooks]

Thanks for the pull request, @tecoholic!

This repository is currently maintained by @bmtcril.

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.

[farhaanbukhsh]

@tecoholic do we need this change since we have idAliases?

[tecoholic]

@farhaanbukhsh Yes and also the upgrade of unit page sidebar component to v2.

We fixed the sticky sidebar issue on the Unit Page Sidebar with V2 and that doesn't have an alias. It seemed better to update all the slot IDs, from alias to ID, along with it.

[farhaanbukhsh]

👍

• ✅ I tested this on the tutor devstack
• ✅ I read through the code
• ❌ I checked for accessibility issues
• ❌ Includes documentation

[bmtcril]

Does this need to be backported to Teak?

[tecoholic]

@bmtcril Yes, we need to make these available in Teak.

The corresponding backport to Authoring MFE has been merged -> openedx/frontend-app-authoring#2178

[farhaanbukhsh]

@tecoholic can you create a backport for this, please. Thanks

@bmtcril I see we don't have a release/teak branch here, do we need it?

[tecoholic]

@farhaanbukhsh I looked around the branches and versioning of this repo. I don't understand it.

The README says,

The plugin is compatible with Tutor 15.0.0 and later and supports Open edX releases from Nutmeg onward.

and there aren't any open-release or release or tutor-xx branches.

Can you kindly give me some pointers of which branch should I use as a base for this backport?

[tecoholic]

@farhaanbukhsh Pinging to check about this backport requirement.

[farhaanbukhsh]

@tecoholic I think we don't need to backport .