chore: add privacy query params to Portfolio navigation

[julesat22]

Description

Added metricsEnabled and marketingEnabled query params to reflect user privacy preferences on navigation to Portfolio. These settings, sent from mobile, will be consumed by the Portfolio to update and align privacy preferences.

Our current privacy opt-in rate has been low since some recent updates to our privacy flow, so we would like to align our privacy settings with the other platforms.

Related issues

Fixes:

Manual testing steps

1. Go to Tokens page in mm mobile
2. Navigate to Portfolio (in a new tab, not in one that has already been opened)
3. See that the privacy params accurately reflect the user's settings in mobile

Example URL:

https://portfolio.metamask.io/?metamaskEntry=mobile&metricsEnabled=false&marketingEnabled=false

Screenshots/Recordings

Before

https://www.loom.com/share/d4034b05e4f7496d9f2ee55416777363

After

With query params attached:

https://www.loom.com/share/4b382b19dcfe460a854ca4f95ebf4819

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.

[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.

[julesat22]

I have read the CLA Document and I hereby sign the CLA

[github-actions]

Bitrise

❌❌❌ pr_smoke_e2e_pipeline failed on Bitrise! ❌❌❌

Commit hash: c7a7423
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/a92a70cf-4a88-4385-bd10-a711066f27ec

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

[github-actions]

Bitrise

✅✅✅ pr_smoke_e2e_pipeline passed on Bitrise! ✅✅✅

Commit hash: b36addf
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/be7d80ec-1be3-462a-9e82-7af2bd2b833d

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
0 New issues
0 Accepted issues

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

See analysis details on SonarCloud

[MarioAslau]

LGTM