Rc/only block conditonal alerts with ff

[Robert-Costello]

Technical Summary

Jira ticket

The BLOCKED_DOMAIN_EMAIL_SENDERS FF was originally intended to block conditional alert emails from being sent. Later changes (linked in the ticket) resulted in all emails being blocked from domains using this FF. The flag is checked in get_valid_recipients which previously depended only on the FF and the presence of domain to determine whether to block emails. If a domain was passed in, the list of recipients returned would be empty. Those later changes made it so that a domain was always passed in, resulting in all emails, conditional alerts and system-related emails, being blocked.
This adds an additional param, is_conditional_alert, to the "send" functions that is passed along to get_valid_recipients. is_conditional_alert is set by checking EmailContent for an associated case, which should only be present for conditional alerts.

Feature Flag

BLOCKED_DOMAIN_EMAIL_SENDERS
and partially overlaps with RICH_TEXT_EMAILS

Safety Assurance

Safety story

Automated test coverage

QA Plan

no QA planned

Rollback instructions

• This PR can be reverted after deploy with no further considerations

Labels & Review

• Risk label is set correctly
• The set of people pinged as reviewers is appropriate for the level of risk of the change

[sentry-io]

🔍 Existing Issues For Review

Your pull request is modifying functions with the following pre-existing issues:

📄 File: corehq/messaging/scheduling/models/content.py

Function	Unhandled Issue
send	AttributeError: 'ConnectMessage' object has no attribute 'couch_id' corehq.messaging.scheduling.tasks.handle_time... Event Count: 3
send	AttributeError: 'ConnectMessage' object has no attribute 'couch_id' corehq.messaging.scheduling.tasks.handle_case_aler... Event Count: 2

---

_{Did you find this useful? React with a 👍 or 👎}