Email Search in ParticipantSearchPopover, Participant hover card component

[wssheldon]

We handle the invalid EmailStr by providing a custom validator in BaseContact model, which will return a default value for invalid emails, instead of failing the entire request.

We add searching by emails in ParticipantSearchPopover

[wssheldon]

@kevgliss figured u should see this change specifically

[wssheldon]

I did test this E2E by modifying an email to some junk value and it works as expected. I get the 422 before, and valid request + default value after this change.

[kevgliss]

Hmmm, this seems a bit counterintuitive to me? If I put in a bad email, I get a 200 and the email is "[email protected]"?

[wssheldon]

agreed this is probably not ideal, it begs the question how we ended up with one in the first place. it might be hard to figure out at this point.

without knowing for sure how it ended up in the database, does it make sense to have a dedicated view and model specifically for read operations, to have the robustness in the event that one somehow slips by (otherwise the entire component stops working, when we really just want the bad value to get handled in some way).