chore: update tutor version constraints to support v22 verawood

[taimoor-ahmed-1]

Description

tutor-contrib-ltistore pins tutor>=19.0.0,<22.0.0, which excludes Tutor v22 and so blocks installing the plugin alongside Verawood or master. This widens the pin to <23.0.0 in both dependencies and the dev extra, following the same shape as the v21 bump in 3adf3ed.

Fixes

Refs #74

Verification

Installed the plugin against tutor==22.0.2 in a clean venv and confirmed every hook it uses still takes effect:

• pip install tutor==22.0.2 + pip install -e plugins/tutor-contrib-ltistore resolves cleanly.
• tutor plugins list shows ltistore installed 19.0.0; tutor plugins enable ltistore succeeds and the environment renders.
• CONFIG_DEFAULTS — tutor config printvalue LTISTORE_PIP_INSTALL returns openedx-ltistore.
• ENV_PATCHES — the rendered env/build/openedx/Dockerfile contains pip install openedx-ltistore.
• CLI_DO_INIT_TASKS — the lms init task is registered, with its waffle-flag and lti_store migration steps intact.

None of the APIs the plugin uses (hooks.Filters.CONFIG_DEFAULTS, ENV_PATCHES, CLI_DO_INIT_TASKS) changed in v22.

Not covered

Issue #74 also asks for the LTI store to be tested with Verawood. This PR only establishes that the plugin is installable and wires itself up correctly under Tutor v22 — it does not verify the runtime behaviour of openedx-ltistore against a running Verawood deployment. Happy to hold this until someone can confirm that, if you would rather the pin move only after a full runtime check.

tutor-contrib-paragon carries the same <22.0.0 pin (plus tutor-mfe) and was bumped together with ltistore last time. I have left it alone here to keep this scoped to #74 — say the word and I will add it.

🤖 Generated with Claude Code

[openedx-webhooks]

Thanks for the pull request, @taimoor-ahmed-1!

This repository is currently maintained by @arbrandes.

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.