fix: SIWE detection on mobile by patching @spruceid+siwe-parser

[jpuri]

Description

Fix SIWE detection on mobile by patching @spruceid+siwe-parser
The module is already patched for this issue on extension: MetaMask/metamask-extension#24138

Related issues

Related to: https://github.com/MetaMask/MetaMask-planning/issues/2278
Related to: https://github.com/MetaMask/MetaMask-planning/issues/4076

Manual testing steps

NA

Screenshots/Recordings

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

Commit hash: d320960
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/1564268a-b693-4b6f-b3cc-9aab2e44a4d8

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

[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

[github-actions]

Bitrise

❌❌❌ pr_smoke_e2e_pipeline failed on Bitrise! ❌❌❌

Commit hash: 31ff4ed
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/cca38459-a4eb-4234-861a-ecaeafb9a889

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