Finalize workspace to devworkspace renaming

[sleshchenko]

What does this PR do?

This PR finalized workspace to devworkspace renaming.
In addition, it also adapts to newer DevWorkspace Client where Che API is introduced + client is initialized in a different way.

What issues does this PR fix or reference?

It's done in the scope of devfile/devworkspace-operator#321.

It depends on che-incubator/devworkspace-client#19
⚠️ After ^ is merged, dependencies should be updated and it should fix PR checks.

Release Notes

Docs PR

[codecov]

Codecov Report

Merging #205 (1523098) into master (345d590) will increase coverage by 0.01%.
The diff coverage is 26.66%.

@@            Coverage Diff             @@
##           master     #205      +/-   ##
==========================================
+ Coverage   50.40%   50.41%   +0.01%     
==========================================
  Files         121      121              
  Lines        4482     4483       +1     
  Branches      740      740              
==========================================
+ Hits         2259     2260       +1     
  Misses       1997     1997              
  Partials      226      226              

Impacted Files	Coverage Δ
src/services/helpers/devworkspace.ts	23.07% <0.00%> (ø)
...rc/services/workspace-client/devWorkspaceClient.ts	18.60% <30.76%> (+0.95%)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 345d590...1523098. Read the comment docs.

[github-actions]

Docker image build succeeded: docker.io/maxura/che-server:che-dashboard-pull-205

[github-actions]

Docker image build succeeded: docker.io/maxura/che-server:che-dashboard-pull-205

[che-bot]

❌ E2E dashboard-next tests failed ❗

See Details

• Jenkins job

• test report

• logs and configs

• Che dashboard-next image:quay.io/crw_pr/che-dashboard:205

• Che server image: quay.io/crw_pr/che-server:205

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

• Use comment "[dashboard-next-ci-test]" to rerun the 'dashboard-next' e2e tests

[che-bot]

❌ E2E dashboard-next tests failed ❗

See Details

• Jenkins job

• test report

• logs and configs

• Che dashboard-next image:quay.io/crw_pr/che-dashboard:205

• Che server image: quay.io/crw_pr/che-server:205

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

• Use comment "[dashboard-next-ci-test]" to rerun the 'dashboard-next' e2e tests