chore: remove all remaining legacy analytics native code

[NicolasMassart]

Description

Remove all Mixpanel analytics native code and dependencies.

Android

• Remove mixpanel native dependencies in android/app/build.gradle
• all native module code in Android related to RCTAnalytics in android/app/src/main/java/io/metamask/nativeModules
• MM_MIXPANEL_TOKEN in .android.env and gradle files

iOS

• Remove mixpanel native dependencies in ios/mixpanel-iphone and ios/Mixpanel.framework
• all native module code in iOS related to RCTAnalytics in ios/MetaMask/NativeModules/RCTAnalytics
• all mixpanel code in ios
• all framework link in ios/MetaMask.xcodeproj
• ios/mixpanel-iphone git submodule
• MM_MIXPANEL_TOKEN in plist files

Common

• all mixpanel properties (search for mixpanel in all the project)
• update remapFlaskEnvVariables mapping of MM_MIXPANEL_TOKEN in scripts/build.sh
• update injectHomePageScripts in app/components/Views/BrowserTab/index.js

Note

update injectHomePageScripts in app/components/Views/BrowserTab/index.js will be done in another PR as it's not mission critical and requires answers form dapp page team.
see #8843

Note

.github/workflows/security-code-scanner.yml uses a Mixpanel tocken that is different from the mobile app one. So no impact on it for the moment except that they have to update on their side as we will terminate the Segment subscription. I notified @NicholasEllul.

Note

TODO added in code related to #8833
todo is an accepted issue in Sonar as there's an issue linked to it.

Related issues

Fixes #8795

Manual testing steps

NA

Screenshots/Recordings

NA

Before

NA

After

NA

Pre-merge author checklist

• I’ve followed MetaMask Coding Standards.
• I've clearly explained what problem this PR is solving and how it is solved.
• I've linked related issues
• I've included manual testing steps
• I've included screenshots/recordings if applicable
• 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.
• I’ve properly set the pull request status:
  • In case it's not yet "ready for review", I've set it to "draft".
  • In case it's "ready for review", I've changed it from "draft" to "non-draft".

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.

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 41.66%. Comparing base (9cf7630) to head (a1098fe).

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #8829      +/-   ##
==========================================
- Coverage   41.66%   41.66%   -0.01%     
==========================================
  Files        1271     1271              
  Lines       30906    30905       -1     
  Branches     3088     3088              
==========================================
- Hits        12877    12876       -1     
  Misses      17250    17250              
  Partials      779      779              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[github-actions]

Bitrise

✅✅✅ pr_smoke_e2e_pipeline passed on Bitrise! ✅✅✅

Commit hash: 3256f16
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/91a46a46-670f-4af6-813c-38daa8ec3ec9

Note

• You can kick off another pr_smoke_e2e_pipeline on Bitrise by removing and re-applying the Run Smoke E2E label on the pull request

[Cal-L]

Left some comments

[github-actions]

Bitrise

✅✅✅ pr_smoke_e2e_pipeline passed on Bitrise! ✅✅✅

Commit hash: 14241b0
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/fc134d94-8613-433c-8f4a-cb5ef5f49de5

Note

• You can kick off another pr_smoke_e2e_pipeline on Bitrise by removing and re-applying the Run Smoke E2E label on the pull request

[Cal-L]

LGTM

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
1 Accepted issue

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

[sethkfman]

LGTM

[Cal-L]

Lgtm!

[metamaskbot]

More than one release label on PR. Keeping the lowest one (release-7.18.0) on PR and removing other release labels (release-7.19.0).