feat: Add performance tracing infrastructure

[OGPoyraz]

Description

• Add initial tracing and performance metrics infrastructure.
  Add the trace, endTrace methods, to be used anywhere in the mobile code to generate a Sentry traces. Implementation is almost same as we have in the extension. The only difference is in extension withIsolatedScope, in mobile withScope is used because @sentry/browser version mismatch in @sentry/react-native. This is also noted in the trace.ts file.
• Add developer options to settings (similar settings added in extension )
  This adds an easily accessible development action menu where devs wants to test some functionality locally. Specifically this PR adds generating nested traces in Sentry.
• New environment variables:
  MM_ENABLE_SETTINGS_PAGE_DEV_OPTIONS : Needs to be set to true in order to show Developer Options in the settings page
  MM_SENTRY_DSN_DEV : This is explicitly set for test-metamask project and the expected value is in the .js.env.example

Related issues

Fixes: https://github.com/MetaMask/mobile-planning/issues/1877

Manual testing steps

1. Go to settings page tab Developer Options
2. Tab Generate Trace Test
3. Open https://metamask.sentry.io/traces/?project=273496&statsPeriod=15m, in this link you will be able to see traces that have been send to test-metamask in last 15 minutes
4. See Developer Test trace is triggered

Screenshots/Recordings

Before

After

Pre-merge author checklist

• I’ve followed MetaMask Contributor Docs and MetaMask Mobile 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.

[socket-security]

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/@sentry/types@7.119.0	None	0	314 kB	sentry-bot

🚮 Removed packages: npm/@sentry/types@6.3.1

View full report↗︎

[Cal-L]

Left some comments

[codecov-commenter]

Codecov Report

Attention: Patch coverage is 82.24299% with 19 lines in your changes missing coverage. Please review.

Project coverage is 55.23%. Comparing base (8dcdd3c) to head (9ed584d).
Report is 71 commits behind head on main.

Files with missing lines	Patch %	Lines
app/util/trace.ts	90.66%	7 Missing ⚠️
...nts/Views/Settings/DeveloperOptions/SentryTest.tsx	64.28%	5 Missing ⚠️
app/util/sentry/utils.js	0.00%	5 Missing ⚠️
app/components/Views/Settings/index.tsx	33.33%	1 Missing and 1 partial ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #11132      +/-   ##
==========================================
+ Coverage   52.75%   55.23%   +2.47%     
==========================================
  Files        1534     1558      +24     
  Lines       36777    37227     +450     
  Branches     4335     4414      +79     
==========================================
+ Hits        19403    20561    +1158     
- Misses      16058    16194     +136     
+ Partials     1316      472     -844     

☔ 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: 3cc85dc
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/c4d4093c-8d44-4a41-ac3d-30731525307e

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]

Nice, LGTM. Feel free to reach out for another approval once the conflicts are fixed.

[github-actions]

Bitrise

✅✅✅ pr_smoke_e2e_pipeline passed on Bitrise! ✅✅✅

Commit hash: 6b55a47
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/663f81d5-dcc4-46d4-b7b5-0e10142b8bb9

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

[sonarqubecloud]

Quality Gate passed

Issues
2 New issues
0 Accepted issues

Measures
0 Security Hotspots
77.5% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[leotm]

lgtm

perhaps like https://github.com/MetaMask/metamask-extension/blob/develop/development/README.md#sentry

we should add a Sentry section here https://github.com/MetaMask/metamask-mobile/blob/main/docs/readme/testing.md

with heading e.g. Generating a trace test that mentions our new env vars, with the odd screenshot or two if it helps