Fix and rework PredefinedNamespace test

[musienko-maxim]

What does this PR do?

• This PR is removed using UI from the tests and works with API calls with oc/kubectl client and fixes logic errors (removing a Workspace from UI after deleting by API)

Screenshot/screencast of this PR

What issues does this PR fix or reference?

https://issues.redhat.com/browse/CRW-5345

How to test this PR?

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 or new feature
• 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.

[dmytro-ndp]

IMHO, replacement of UI test with API test is too big change for the task to target issue: "fix test workspace removal after the test execution".
New test scenario is not actually covering Dashboard and Che server behavior when there is pre-defined user namespace.

What do you think about only removal of the next suites, which don't make sense after user workspace and namespace have been removed from cluster in previous suiteTeardown():

	suiteTeardown('Re-login with test user', async function (): Promise<void> {
		if (OAUTH_CONSTANTS.TS_SELENIUM_OCP_USERNAME !== userName) {
			await loginTests.logoutFromChe();
			await loginTests.loginIntoChe();
		}
	});

	suiteTeardown('Open dashboard and close all other tabs', async function (): Promise<void> {
		await dashboard.openDashboard();
		await browserTabsUtil.closeAllTabsExceptCurrent();
	});

	suiteTeardown('Stop and delete the workspace by API', async function (): Promise<void> {
		await testWorkspaceUtil.stopAndDeleteWorkspaceByName(WorkspaceHandlingTests.getWorkspaceName());
	});

?

P.S. Test screencast shows another problem - workspace failed to start:

output.32.webm

Did you try to reproduce the error manually?

[musienko-maxim]

I can't entirely agree with saving the UI part.
This test is not responsible for communicating with the dashboard. One reason for creating a workspace from the dashboard was the absence of the possibility generating DevFiles. The main goal of the test is to check that a DW object is created in the dedicated Openshift project.
About the error on the screencast, I ran the test on my latest instance manually: create the Predefined NS by oc client and create the Empty workspace from the Dashboard - this problem was not reproduced.
I can check it manually one more time - to make sure 100% that the problem on the screencast is not reproduced.

[dmytro-ndp]

@musienko-maxim : the test was initially created to check user namespace provisioning using Dashboard.

@ibuziuk, @l0rd: could you, please, say if it would be enough to test user namespace provisioning at DevWorkspace level only not using Che Dashboard and Che Server?

[ibuziuk]

+1 to remove the UI logic and fallback on oc / kubect