Add initial status to drip destination

[stevedrip]

The default behavior for status is a footgun for users. Prefer the more forgiving initial_status instead. When combined with status_updated_at this will updated a person's status as if the change happened at that timestamp. When status_updated_at is missing, any existing status will take priority.

Previously, we assumed that the user would always want to update the status when identifying a person. We defaulted to unsubscribing, and at the current timestamp. This has proven to be a poor assumption in practice. With this new behavior, if the status_updated_at was intended to be passed but missing, we won't modify the person's status in drip.

Testing

Include any additional information about the testing you have completed to
ensure your changes behave as expected. For a speedy review, please check
any of the tasks you completed below during your testing.

• Added unit tests for new functionality
• Tested end-to-end using the local server
• [If destination is already live] Tested for backward compatibility of destination. Note: New required fields are a breaking change.
• [Segmenters] Tested in the staging environment
• [Segmenters] [If applicable for this change] Tested for regression with Hadron.

[joe-ayoub-segment]

to @jacobpmeyer and Developer Rotation person - I'll take this PR so no need to follow up on it.

hi @stevedrip - thanks for the PR.
The code looks good. There is a failing test from another Integration though, so can you please pull in the latest code from Segment's main branch please?

Thank you!
Joe

[jacobpmeyer]

to @jacobpmeyer and Developer Rotation person - I'll take this PR so no need to follow up on it.

hi @stevedrip - thanks for the PR. The code looks good. There is a failing test from another Integration though, so can you please pull in the latest code from Segment's main branch please?

Thank you! Joe

Hey @joe-ayoub-segment. I work with @stevedrip. I went ahead and merged main into this branch