fix: E2E: quarantine import-wallet-account tests

[chrisleewilcox]

Description

This tests has become flaky and will need to go to quarantine.

Related issues

Fixes:

Manual testing steps

1. Go to this page...

Screenshots/Recordings

Before

https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/2122f77b-77f6-469e-8bd0-c367feb37fca?tab=workflows

After

https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/66b628b2-ffbd-4c48-94c2-54199ca71469?tab=workflows

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: 282a28c
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/66b628b2-ffbd-4c48-94c2-54199ca71469

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: db5cd81
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/54206758-9f62-4269-90ad-798882840cc2

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 SonarCloud

[Andepande]

LG