Explanation

Why: currently when we run the script for executing all e2e tests, they are stopped and script is terminated if a failure is encountered. There are certain occasions that we want to continue them running.
For example, on the MV3 job, we want to run all the tests to see all failing tests. Or a developer might want to run them all to see all the failures at once.
There are also cases when we want the tests to fail fast, i.e. capture errors fast on a circle ci run, or avoid spending too much resources on circle ci.
For this reason we'll include this change as an option.

What: we'll include an option for running all e2e tests no matter if they fail.

How:

• We'll make it the default option for the MV3 run, for now, as it is convenient to see ALL the failing tests.
• Anyone can add this option flag when running their tests locally by adding the --resume flag.

More Information

Resolves #16192

Screenshots/Screencaps

Before

• Run-all script terminated on failure

After

• Run-all script continues after failure if --resume option is passed

Manual Testing Steps

Locally

1. Change last assertion on the account-details.spec.js file in order to make it fail:
   assert.equal(await qrCode.isDisplayed(), "sdkfha");
2. Run all tests and see how they continue running after failure if resume option is passed
   yarn test:e2e:chrome --resume

On Circle CI
Check that MV3 e2e testcases continue after failure, on circle ci job.
https://app.circleci.com/pipelines/github/MetaMask/metamask-extension/29114/workflows/dc9db3da-099a-44a5-8896-dad6aa71b091/jobs/756717

Pre-Merge Checklist

• PR template is filled out
• IF this PR fixes a bug, a test that would have caught the bug has been added
• PR is linked to the appropriate GitHub issue
• PR has been added to the appropriate release Milestone

+ If there are functional changes:

• Manual testing complete & passed
• "Extension QA Board" label has been applied