fix: Move the SnapExecutionService render up in the stack

[Cal-L]

Description

This fixes the issue on main where there are errors accessing snap execution webview. The fix was to move the SnapExecutionWebView up in the stack since it needs to render before being accessed by the Engine

Thread - https://consensys.slack.com/archives/C07M5L4U51U/p1741817154708019

Related issues

Fixes: https://consensys.slack.com/archives/C07M5L4U51U/p1741817154708019

Manual testing steps

1. Run flask build ensuring that Solana accounts are enabled
2. Try to add a Solana account
3. Solana account creation should work

Screenshots/Recordings

Before

After

Reach out to @Cal-L for vid

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: 40e2e1d
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/a9866e4f-9403-4898-b15b-d11699bed9b2

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 started on Bitrise...🔄🔄🔄

Commit hash: 3b58739
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/d0ba5ebc-6ee7-45f8-b82b-1a06527a7084

Note

• This comment will auto-update when build completes
• 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
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud