Pass segmentId to automation processing

[sausage-todd]

Changes proposed ✍️

What

🤖 Generated by Copilot at b7c7ad4

Added support for segment-based automations for new activity and new member triggers. Modified the message types, SQS functions, and workers to pass and use the segmentId property. Updated the memberService to send the segmentId when creating or updating a member.
​

🤖 Generated by Copilot at b7c7ad4

To automate actions with ease
We added segmentId keys
To the SQS messages
And the worker processes
That handle the members and activities

Why

How

🤖 Generated by Copilot at b7c7ad4

• Add segmentId parameter to new activity and new member automation workers and messages (link, link, link, link, link, link, link, link, link)
• Pass segmentId from options to sendNewMemberNodeSQSMessage function in memberService.ts (link)

Checklist ✅

• Label appropriately with Feature, Improvement, or Bug.
• Add screehshots to the PR description for relevant FE changes
• New backend functionality has been unit-tested.
• API documentation has been updated (if necessary) (see docs on API documentation).
• Quality standards are met.