Braze requires email to formatted correctly, connector fails on erasure

[SteveDMurphy]

Bug Description

The Braze connector requires email to be formatted like an email (i.e. [email protected])

We currently use the default masked string for this connector, resulting in a 400 error

We should format the masked string to look like a valid email

Steps to Reproduce

This requires a valid Braze account with a known email
Try to update the email of a user to a random string
See the error response

Expected behavior

The data should be masked appropriately

Screenshots

{
    "message": "Valid data must be provided in the 'attributes', 'events', or 'purchases' fields.",
    "errors": [
        {
            "type": "The value provided for the 'email' field is not a valid email.",
            "input_array": "attributes",
            "index": 0
        }
    ]
}

Environment

• Version: 2.20.2
• OS: Darwin
• Python Version: 3.10
• Docker Version:

Additional context

Found when troubleshooting a connector issue, it looks like we do something similar already for Domo -> https://github.com/ethyca/fides/blob/main/src/fides/api/service/saas_request/override_implementations/domo_request_overrides.py#L36-L37

This could be nice if we had a general fides_meta attribute to select from a required masked format (i.e. email, phone, etc.)

[SteveDMurphy]

@galvana I am going to take a stab at a quick fix here for Braze but wanted to tag you for visibility (as well about a longer term solution maybe?)