E2E job parallelization by user role and functionality

[yonasberhe23]

Currently, admin and standard user tests run asynchronously but we want them to run in parallel. To handle this, lets pull the Rancher setup spec out of the admin test run and put it in its own step, that way the setup step would precede both the admin and standard user test steps and they can run in parallel.

For more details see conversation here.

NOTE: standard_user creation has been added in the Rancher setup test.

[richard-cox]

This should be done alongside #9064

[cnotv]

I think that if the only issue here is to initialize the Rancher instance, we may rather create a function for that.

In the current state it's necessary to build and run an image of Rancher for both to have 2 separated environments.

[cnotv]

I can see that the issue here is not about the setup at all, we have also to create the user as admin first. I was not aware of the update where we create the user in the setup.

[cnotv]

This should be done alongside #9064

That's more about run tests in parallels, not jobs in parallel, so are 2 different cases.

[cnotv]

After talking to @richard-cox and @nwmac we decided to try more job splitting by path/tag, so we can create categories or isolate long jobs which cause issues.

[cnotv]

@yonasberhe23 @richard-cox Are we sure the tests are idempotent? I have run 5 times in parallel and the same tests keep failing.