FC-73 pr for edx platform repository (Creating waffle flag for integration towards created_submission in the edx-submission repo)

[gabrielC1409]

Description

This pull request introduces several improvements and updates to the xmodule/layer module of the edx-platform repository. The main changes include:

Refactoring of xqueue_interface.py and xqueue_submission.py: The functions for sending and handling responses that a student sends within an exercise created in a course have been optimized. For this, the original functionality of sending the submission to Xqueue was maintained, but for this improvement a Waffle Switch was created, where within the LMS Administration it was possible to create and from the tutor env in the development.py file this environment variable is found pointing to the Switch created in the LMS Administration. This Switch was created within Xqueue_interfaces.py when you want to test or not this new functionality of sending the submit to created_submission.

Motivation:

These improvements aim to optimize the performance and maintainability of the XQueue-related code, ensuring a more robust and efficient integration into the evaluation workflow.

Tests performed:

The tests in test_xqueue_interface.py and test_xqueue_submission.py have been reviewed and updated to ensure compatibility with the new modifications and improve test coverage.

Additional considerations:

No negative impacts on other parts of the system are anticipated, as the changes are limited to the xmodule/layer module.

Recommendations for review:

A detailed review of the modified functions in xqueue_interface.py and xqueue_submission.py, as well as the new tests added in the corresponding files, is suggested.

[openedx-webhooks]

Thanks for the pull request, @gabrielC1409!

This repository is currently maintained by @openedx/wg-maintenance-edx-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.

---

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.