Refactor mailchimp email and serviceUserProfiles

[annarhughes]

What changes did you make?

Refactors email functionality for existing automated emails send from bloom - the Impact measurement email and the therapy feedback email. Replaces mandrill + mailchimp setup, with mailchimp automations and synced user profiles data to trigger email automations. The existing similar crisp functionality was refactored to improve the DRYness and performance - all service profile updates are handled together in serviceUserProfiles.ts

The logic flows are as follows:

• User account created -> create user in mailchimp/crisp with profile data and partner access data
• User adds new partner access -> update mailchimp/crisp users partners data
• User creates/updates/cancels therapy session -> update mailchimp/crisp users therapy dates and total sessions redeemed/remaining
• User starts/completes course session -> update mailchimp/crisp users course data
• New course created -> creates new course fields on mailchimp user profile

Mailchimp automations will to trigger impact measurement email based on signed_up_at date
Mailchimp automation will trigger therapy feedback email based on first_therapy_session_at date

This PR completes the transition of existing emails for Bloom, however it is now much easier to send additional one-off and automated emails using mailchimp user fields, and/or mailchimp events

Why did you make the changes?

We are introducing mailchimp automations for our transactional (user-triggered) emails across Chayn services. We previously used Mandrill as an add on for transactional emails, which is currently being integrated into mailchimp. However mailchimps existing automations now seems to be the best tool for most of our email requirements, including our Bloom feedback emails. So we’re moving the current functionality for bloom emails to automations.