fix: Remove run all tests section

[chrisleewilcox]

Description

Run all test locally with a single command is not recommended as running all tests are not ran in the same manner on CI. This will also prevent some confusion with new contributors running all test the first time which will take a long time. Removing the run all test section will make it more clear to new contributors to run a specific test or a suite of tests as currently documented and is more align with how we run test in CI.

Related issues

Fixes: team members running into issue attempting to run e2e test on their local system for the first time.

Manual testing steps

1. document running a single test
2. document running a suite of tests
3. no document for running all test with a single command

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 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