chore: remove web_fragments dependency, bump requirements

[Kelketek]

Description

This merge request removes web_fragments as a direct dependency and upgrades XBlock. It also upgrades packages generally since the dependencies were recalculated.

Supporting information

Link to other information about the change, such as Jira issues, GitHub issues, or Discourse discussions.
Be sure to check they are publicly readable, or if not, repeat the information here.

Testing instructions

1. Set up a devstack (or wait for the sandbox) with this branch
2. Create the standard blocks in studio and publish them in a course
3. View them in the LMS and verify they render as expected.

[openedx-webhooks]

Thanks for the pull request, @Kelketek!

This repository is currently maintained by @openedx/wg-maintenance-openedx-platform.

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.

[Kelketek]

@feanil I've made this PR to remove the dependency and re-run upgrades, but it looks like upgrading is throwing in at least one change which is breaking things. How would you prefer I handle this? Should I, instead of running upgrades, just remove the web-fragments dependency, and run make compile without make upgrade, and then let things move forward in the normal upgrade process y'all normally do?

[Kelketek]

@feanil Upgrading today went cleanly, and this is ready for you, now. Sandbox seems to be fine.

[Kelketek]

@feanil Do you have an idea when you'll be able to take a look at this? Also the code coverage check failed but it seems unrelated to anything done here (no actual code is changed, just requirements files.)

[feanil]

Looking now! :-)

[Kelketek]

Yay! Thanks, @feanil ! Can you archive web_fragments? Also, what repo should I look at removing next? :)

[feanil]

@Kelketek can you make an axim-engieering request for the archival. We'll want to track that over there and the on-call person can take care of it.

[Kelketek]

@feanil Done! openedx/axim-engineering#1718