fix(12945): privacy mode and account selection bottom sheet

[vinnyhoward]

Description

Issue: Privacy mode was not hiding account balances within the account selector bottom sheet at all

Solution: Have the account selector bottom sheet component subscribe to the privacyMode prop which hides the balance of all accounts, introduce the disablePrivacyMode route params so that the account selector bottom sheet can opt out of privacy mode completely for certain flows. Cases where this is needed is in the send flow and swap flow. We do not hide the balance when a user needs to switch between accounts when sending/swapping

Related issues

Fixes: #12945

Manual testing steps

1. Turn on privacy mode by clicking the eye icon within the portfolio balance at the top
2. Click on the account selector in the top to confirm balances for other accounts are hidden
3. Goto send and swap flow to confirm balances are NOT hidden even when privacy mode is ON

Screenshots/Recordings

Send Flow

Before	After

Swap Flow

Before	After

Before

NA

After

NA

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.

[github-actions]

Bitrise

✅✅✅ pr_smoke_e2e_pipeline passed on Bitrise! ✅✅✅

Commit hash: 2abd70e
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/aae00973-5ef1-4ee0-8bb3-7e46a545d07a

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
50.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[wachunei]

Ramp changes LGTM

[OGPoyraz]

Confirmation changes LGTM

[Cal-L]

LGTM