3.1.0 | Include a Braze campaign id in enterprise code/offer emails

https://github.com/edx/ecommerce-worker/pull/153
https://openedx.atlassian.net/browse/ENT-5285

Upgrade to Django 3.2

What's Changed

• feat! Upgrade to Django 3.2 by @UsamaSadiq in https://github.com/edx/ecommerce-worker/pull/147

Full Changelog: edx/ecommerce-worker@2.3.0...3.0.0

Added support for Django 3.2

What's Changed

• BOM-2640: Upgrade & Codemods by @mzulqarnain1 in https://github.com/edx/ecommerce-worker/pull/144

Full Changelog: edx/ecommerce-worker@2.2.2...2.3.0

Added advisory to be clear that all merges must be deployed to PR template and README

2.2.2

docs: Added PR template advisory to be clear that all merges must be …

Updated Braze client to send emails to all users

Updated the Braze client to send emails to all users, irrespective of their "opt-in" status

Added file attachments to the Braze client and usages

Added file attachments to the Braze client and usages.

Remove special characters from sender_alias

• Remove special character from the sender_alias field so form field is validated by Braze.

Added reply_to option for braze email messages

Added reply_to option for braze email messages

Fix celery import definition

The celery import entry points did not match ecommerce's celery routing. This should sync them again.

Remove sailthru and braze modules in favor of generic email module

• The sailthru/v1 module has been removed completely (no longer supported)
• The braze/v1 module has been abstracted as just email/v1 without any specific references to braze
• email/v1 has the same API as sailthru/v1 had, with the small addition of did_email_bounce