chore: Chore/12628 create navigation provider

[Cal-L]

Description

This PR cleans up the NavigationService and moves the navigation provider further up in the app stack. This ensures that the provider's children has access to the navigation object. This should reduce the number of cases where navigation is accessed before the navigation provider is ready. In theory, this should eliminate the navigation issue WRT WalletConnect service altogether - #12628. The metric to measure this improvement is looking at the reduction of this event - https://metamask.sentry.io/issues/4909236583/?environment=production&project=2299799&query=is%3Aunresolved%20issue.priority%3A%5Bhigh%2C%20medium%5D%20%22navigation%22&referrer=issue-stream&sort=date&statsPeriod=90d&stream_index=0

Related issues

Fixes: #12628

Manual testing steps

• App should function normally
• Build the app as usual
• Navigation works as soon as app starts
• Deeplinking works as expected

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.

[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 failed on Bitrise! ❌❌❌

Commit hash: e923754
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/c7c6c977-bb4e-4b33-8766-ac71e9cd63e4

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

Tip

• Check the documentation if you have any doubts on how to understand the failure on bitrise

[github-actions]

Bitrise

❌❌❌ pr_smoke_e2e_pipeline failed on Bitrise! ❌❌❌

Commit hash: b466761
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/75f42644-9d93-45ab-9b3c-1d50121290be

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

Tip

• Check the documentation if you have any doubts on how to understand the failure on bitrise

[github-actions]

Bitrise

❌❌❌ pr_smoke_e2e_pipeline failed on Bitrise! ❌❌❌

Commit hash: 64c2bcb
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/bf386fc2-eb46-48a8-adb5-5e7b30ed34bc

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

Tip

• Check the documentation if you have any doubts on how to understand the failure on bitrise

[sonarcloud]

Quality Gate passed

Issues
7 New issues
0 Accepted issues

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

See analysis details on SonarQube Cloud