Fix E2E run/up check

[diegocurbelo]

Changes proposed in this Pull Request:

This PR fixes the check when running npm run test:e2e; it now correctly exits with an error if the containers are not running:

It also sets the project-name for npm run test:e2e-up to avoid orphaned containers when running npm run test:e2e-down

Testing instructions

1. Checkout the develop develop
2. Make sure the E2E containers are stopped
3. Run npm run test:e2e-setup
   
4. Run npm run test:e2e-up, and check that the project name used is env
   
5. Run npm run test:e2e-down and verify it has no effect.
6. Checkout this branch
7. Re-run npm run test:e2e-setup and check that the descriptive error message is displayed:
   
8. Manually delete the env containers created during step 4.
9. Re-run npm run test:e2e-up, and check that the correct project name is used:
   
10. Re-run npm run test:e2e-down, and verify that the containers are correctly removed.

---

• Covered with tests (or have a good reason not to test in description ☝️)
• Tested on mobile (or does not apply)

Changelog entry

• This Pull Request does not require a changelog entry. (Comment required below)

Changelog Entry Comment

Comment

Post merge

• Added testing instructions to the Release Testing Instructions wiki page (or does not apply)
• Added the needs docs label (or does not apply)
• Included this PR in the Release Thread scope (or does not apply)

[Mayisha]

Works as described 🎉

Before

After