Add kubetest2 deployer for e2e testing

[breuerfelix]

How to categorize this PR?

What this PR does / why we need it:

Which issue(s) this PR fixes:
Fixes #

Special notes for your reviewer:

Breaking changes:

/hold still WIP

[ske-prow]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[ske-prow]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign jamand for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[breuerfelix]

somehow i don't like that this is split up in "bootstrap" and "ske cluster provisioning". To me all steps are equally important in terms of bootstrapping, also deploying the csi helmchart will be the last step.
i would like to organize this a little different.
add another folder, lets name it "bootstrap" if you will, inside there are multiple go files for every step.
project.go
serviceaccount.go
ske.go
csi.go
...
Each expose an ensure function. "ensureProject", "ensureCluster" etc.
The Up() function just calls these functions one after another :) and each function itself is idempotent.

This would overall help with getting through the code and understanding when which step is happening and each step can be encapsulated really nice :)

WDYT?

[xoxys]

Im going with a flattened/restructured file list for now. A bootstrap/ folder would result in a new go package, so ensureProject etc. couldn't stay methods on *Deployer and we would have to refactor a lot. The bootstrap_*.go prefix gives the same readability IMO. What do you think?