feat: add ability to override middlewares for recurring nudges

[kaustavb12]

Description

This PR brings two changes to all the management commands based on SendEmailBaseCommand:

1. Adds the ability to pass a list of middlewares to override the default list of middlewares used to emulate HTTP requests in the async message tasks - This would be very helpful for instances running custom middlewares that they want to apply to recurring messages.
2. Adds the ability to run the management commands for all sites by not passing any site domain. This would be helpful for instances running lots of sites that would otherwise need to run the same command individually for each site.

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 this branch in a sandbox.
2. Set up two or more sites with course_org_filter setup for each site to map it to a unique org.
3. Create courses for each site/org and enroll in them.
4. Make sure date conditions for recurring nudges are satisfied for the enrollments and run the send_recurring_nudge command without passing any site domain name.
5. Make sure emails from each site/org are triggered.

Deadline

"None" if there's no rush, or provide a specific date or event (and reason) if there is one.

Other information

Private Ref : BB-9883

[openedx-webhooks]

Thanks for the pull request, @kaustavb12!

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.

[samuelallan72]

👍

• I tested this: compared with open-craft/edx-platform#790, tested on a sandbox on open-craft/edx-platform#790
• I read through the code
• I checked for accessibility issues
• Includes documentation
• [N/A] Added to the Code Drift project board (for backports)

[farhaanbukhsh]

@kaustavb12 can you rebase the PR please :)

[farhaanbukhsh]

The code looks good why is the code coverage no passing? Can we fix that?

[kaustavb12]

@farhaanbukhsh

PR rebased. Not sure why code coverage was failing then, perhaps it was just being flaky.
All checks have passed now though. Please take a look. :)

[farhaanbukhsh]

👍

• ✅ I tested this on the devstack and it ran gracefully.
• ✅ I read through the code
• ❌ I checked for accessibility issues
• ❌ Includes documentation

[edx-pipeline-bot]

2U Release Notice: This PR has been deployed to the edX staging environment in preparation for a release to production.