backport chore: provide logo url from backend for batch enrollment email (#35138)

[mudassir-hafeez]

Ticket for internal tracking

https://github.com/mitodl/hq/issues/4923

Description

This PR is a backport of the changes made in PR #35138 to the open-release/quince.master branch.

For the past couple of years, edX has supported a logo URL from the backend for Bulk Email and edX ACE emails. But, this does not have similar support for emails using batch enrollment. Not sure if it is intentional or could have some other reasons but it causes the logo URL to be missed if it needs to be passed from the backend similar to Bulk Email and edX ACE emails.

This pull request addresses the logo not appearing in batch enrollment emails when the logo URL is set in the backend and accessed in the template(or custom theme) similar to how edX Bulk or ACE email use.

Useful information to include:

• No UI changes were made, so no screenshots are necessary.

Supporting information

• Related pull request in edX platform.

Testing instructions

• Ensure that LOGO_URL_PNG_FOR_EMAIL or any of the settings accessed in this code is set.
• Go to the Membership tab in the Instructor Dashboard with a user having staff access.
• Send a Batch Enrollment or Batch Beta Tester email.
• Verify that the logo appears correctly in the email.

Other information

• This change is isolated to the email template logic and does not depend on other changes.
• No database migrations are involved.

[openedx-webhooks]

Thanks for the pull request, @mudassir-hafeez!

What's next?

Please work through the following steps to get your changes 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.

🔘 Let us know that your PR is ready for review:

Who will review my changes?

This repository is currently maintained by @openedx/wg-maintenance-edx-platform. Tag them in a comment and let them know that your changes are ready for review.

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.

[ziafazal]

👍

[openedx-webhooks]

@mudassir-hafeez 🎉 Your pull request was merged! Please take a moment to answer a two question survey so we can improve your experience in the future.