feat: add server metametrics id

[Prithpal-Sooriya]

Description

Uses an optional server metametrics ID. When set and provided, this ID will be the source of truth for metric events.
This provides better analytics for users who are logged in.

NOTE - this does not change anything really for existing users. This will (once our system enables this feature) will decrease the number of users (the same user on multiple devices).

We can have a larger discussion on this.

Related issues

Fixes:

Manual testing steps

N/A until this feature is enabled on our services.

Once this does go live:

Install 1:

1. Use existing account with same SRP
2. Continue onboarding, ensure that metametrics is enabled.
3. Investigate segment calls and see which userId is sent.

Install 2:

1. Uninstall/Reinstall or install on another browser/device
2. Use existing account with same SRP
3. Continue onboarding, ensure that metametrics is enabled.
4. Investigate segment calls and see which userId is sent.
5. Check if the userId are now the same

Screenshots/Recordings

N/A

Before

N/A

After

N/A

Pre-merge author checklist

• I’ve followed MetaMask Coding Standards.
• I've completed the PR template to the best of my ability
• I’ve included tests if applicable
• I’ve documented my code using JSDoc format if applicable
• I’ve applied the right labels on the PR (see labeling guidelines). Not required for external contributors.

Pre-merge reviewer checklist

• I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed).
• I confirm that this PR addresses all acceptance criteria described in the ticket it closes and includes the necessary testing evidence such as recordings and or screenshots.

[github-actions]

CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes.

[Prithpal-Sooriya]

As comment mentioned, we need this to be used on Mobile. Seeing that the metametrics controller is still inside the extension, my guess is that mobile uses a different approach.

[Prithpal-Sooriya]

Effected Segment Events:

• Identify
• TrackPage
• TrackEvent

[legobeat]

Same SRP does not necessarily imply same user (best security-practices aside).

How does this distinguish one user with a new device from e.g. one user selling their private keys (delivered through SRP) to another user with a separate device, or multiple users sharing a wallet by instantiating separate devices with the same SRP?

Correlating separate users on separate devices under a single metrics ID seems problematic.

[Prithpal-Sooriya]

We've had a recent discussion with the analytics team, we are now intending on using the same unique client metametrics, but just handling lineage on the back-end.

[Prithpal-Sooriya]

@legobeat

We've recently decided that we won't be using the server metametrics ID on future events (only keeping a lineage) - so will close this PR & open a new one with the relevant changes. I'll make sure to link it.

How does this distinguish one user with a new device from e.g. one user selling their private keys (delivered through SRP) to another user with a separate device, or multiple users sharing a wallet by instantiating separate devices with the same SRP?

This is a great point! I will discuss this with our team & the analytics team. Events now will still be unique, but need to keep this in mind when we store and manage the lineage/linked metametrics ids.

[Prithpal-Sooriya]

I'm closing this PR as the feature has changed from discussing with the analytics team.

A new PR (#24555) will be opened soon that does not use the server metametrics id on future events.