chore(metrics): Segment dependency cleanup

[tianrunhe]

Description

Last piece to completely remove Segment dependencies:

1. Renamings:
   • client/hooks/useSegmentTrack.ts → client/hooks/useClientSideTrack.ts
   • server/graphql/mutations/helpers/sendAccountRemovedToSegment.ts → server/graphql/mutations/helpers/sendAccountRemovedEvent.ts
   • server/graphql/mutations/helpers/sendPokerMeetingRevoteToSegment.ts → server/graphql/mutations/helpers/sendPokerMeetingRevoteEvent.ts
2. client/utils/safeIdentify.ts: Replace Segment's identify to Amplitude's identify
3. server/graphql/webhookGraphQLHandler.ts: I'm not sure why we need the SEGMENT_FN_KEY here and why we need double encryptions?

Final checklist

• I checked the code review guidelines
• I have added Metrics Representative as reviewer(s) if my PR invovles metrics/data/analytics related changes
• I have performed a self-review of my code, the same way I'd do it for any other team member
• I have tested all cases I listed in the testing scenarios and I haven't found any issues or regressions
• Whenever I took a non-obvious choice I added a comment explaining why I did it this way
• I added the label One Review Required if the PR introduces only minor changes, does not contain any architectural changes or does not introduce any new patterns and I think one review is sufficient'
• PR title is human readable and could be used in changelog

[tianrunhe]

I don't quite understand why we need to use the SEGMENT_FN_KEY here, and also why need to encrypt once with it and then another time with the SERVER_SECRET. I changed it to just encrypt once.
Let me know if it's gonna break!

[Dschoordsch]

Well, that's an interesting one! Required some digging, but now I know what was going on: Segment used to request additional data for an event from the app, see this PR. For this we sent the signed timestamp with each event.
We're not doing this anymore, this file and its references should be removed.

[Dschoordsch]

Did not test yet. You've uncovered some long forgotten code there which should be deleted before merging

[Dschoordsch]

Well, that's an interesting one! Required some digging, but now I know what was going on: Segment used to request additional data for an event from the app, see this PR. For this we sent the signed timestamp with each event.
We're not doing this anymore, this file and its references should be removed.

[sentry-io]

Suspect Issues

This pull request was deployed and Sentry observed the following issues:

• ‼️ TypeError: null is not an object (evaluating 'window.localStorage.getItem') <anonymous>(packages/client/components/Analytic... View Issue

_{Did you find this useful? React with a 👍 or 👎}