Added new test constant for workspace stop timeout, 30s by default

[ScrewTSW]

What does this PR do?

• Extends the amount of time the tests are waiting for the workspace to switch to stopped state

Screenshot/screencast of this PR

N/A

What issues does this PR fix or reference?

redhat-developer/rh-che#2025

How to test this PR?

• Go into Eclipse repository che/tests/e2e
• Run npm i and verify that all packages install without errors
• Run tsc and verify that no errors are present
• Export following variables:
  • TS_SELENIUM_BASE_URL
  • TS_SELENIUM_MULTIUSER=true
  • NODE_TLS_REJECT_UNAUTHORIZED=0
  • TS_SELENIUM_LOG_LEVEL="TRACE"
  • TS_SELENIUM_USERNAME
  • TS_SELENIUM_PASSWORD
• Run npm run test-java-vertx to execute the smoke test devfile and verify that the tests are working correctly or run entire suite using npm run test-all-devfiles
• Tests should pass without a failure

PR Checklist

As the author of this Pull Request I made sure that:

• The Eclipse Contributor Agreement is valid
• Code produced is complete
• Code builds without errors
• Tests are covering the bugfix
• The repository devfile is up to date and works
• Sections What issues does this PR fix or reference and How to test this PR completed
• Relevant user documentation updated
• Relevant contributing documentation updated
• CI/CD changes implemented, documented and communicated

Reviewers

Reviewers, please comment how you tested the PR when approving it.

[che-bot]

✅ E2E Happy path tests succeed 🎉

See Details

• Jenkins job

• logs and configs

• Happy path tests DevFile

• image: maxura/che-server:18608

Tested with Eclipse Che Multiuser User on K8S (minikube v1.1.1)

• Use comment "[crw-ci-test]" to rerun happy path E2E test.
• Use comment "[crw-ci-test --rebuild]" to re-build the images and rerun happy path E2E test.

[ScrewTSW]

[ci-build]