Feat/mmprovider2

[abretonc7s]

Description

This PR implements the infrastructure for multichain E2E testing focused specifically on EVM networks. The changes include:

1. Fixed static server URL handling for the multichain test dapp by adding path rewriting for /test-dapp-multichain/ prefixes
2. Added proper configuration in fixture-helper.js to serve the multichain test dapp
3. Created initial E2E test example that loads the multichain test dapp

The goal is to replicate the core test modules from the MetaMask extension's multichain E2E tests, starting with basic dapp connectivity and gradually implementing the full suite of tests for wallet_createSession, wallet_invokeMethod, wallet_getSession, and wallet_revokeSession.

At this stage, we're focusing only on EVM networks as we're not yet ready for non-EVM network testing.

Run with:

# Load environment and run all multichain tests
source .e2e.env && MULTICHAIN=1 yarn test:e2e:ios:debug:run e2e/specs/multichain/wallet-createSession.spec.ts e2e/specs/multichain/wallet-getSession.spec.ts e2e/specs/multichain/wallet-invokeMethod.spec.ts e2e/specs/multichain/wallet-notify.spec.ts e2e/specs/multichain/wallet-revokeSession.spec.ts e2e/specs/multichain/wallet-sessionChanged.spec.ts

# Run individual test files
source .e2e.env && MULTICHAIN=1 yarn test:e2e:ios:debug:run e2e/specs/multichain/wallet-createSession.spec.ts

Related issues

Fixes:

Manual testing steps

1. Go to this page...

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.

[sonarqubecloud]

Quality Gate failed

Failed conditions
14.3% Coverage on New Code (required ≥ 80%)

See analysis details on SonarQube Cloud