Backport fix: enable markdown editor in libraries

[bradenmacdonald]

Description

The markdown problem editor wasn't available in libraries, but probably unintentionally.

Supporting information

Don't merge yet - there is a minor bug with this: #2099

Testing instructions

Create a new problem in a library. Switch to markdown editor.
Confirm that if the waffle flag is modified, the markdown option is no longer available.

Other information

[openedx-webhooks]

Thanks for the pull request, @bradenmacdonald!

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.

---

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.

[bradenmacdonald]

FYI @Anas12091101 @kdmccormick

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Please upload report for BASE (release/teak@fcdf1fd). Learn more about missing BASE report.

Additional details and impacted files

@@               Coverage Diff               @@
##             release/teak    #2098   +/-   ##
===============================================
  Coverage                ?   93.90%           
===============================================
  Files                   ?     1148           
  Lines                   ?    24039           
  Branches                ?     5082           
===============================================
  Hits                    ?    22573           
  Misses                  ?     1398           
  Partials                ?       68           

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

[bradenmacdonald]

@kdmccormick Now that #2112 is merged and will presumably be backported soon, I'd like to merge this backport - would you mind reviewing?

[kdmccormick]

Just to make sure I'm clear -- this isn't a direct backport, but is rather a meant to achieve the same functionality as #2068 (comment) minus the refactoring? If so can you make note of that in the commit?

[bradenmacdonald]

@kdmccormick Sure, I added that note to the commit and cherry-picked in the other fix from #2127

[kdmccormick]

Great, I will let you know once I confirm these both on the PR sandbox.

@farhaanbukhsh , any objections to both this and #2127 being backported to Teak? It's just more bugfixes for the Switch-to-markdown option in the Problem editor.

[farhaanbukhsh]

@kdmccormick nope, onwards and upwards for more bugfixes.

[bradenmacdonald]

I don't see any sandbox here? I asked on Slack about it. I guess we're waiting on that unless someone can test manually.

[open-craft-grove]

Sandbox deployment successful 🚀
🎓 LMS
📝 Studio
ℹ️ Grove Config, Tutor Config, Tutor Requirements

[bradenmacdonald]

Tested creating markdown problems on the sandbox in a library and a course and everything is working well :)