[e2e] Decoupling cloud providers from the e2e testing framework

[neolit123]

parent issue:
#75601

tests that a part of the framework and the framework as a whole should not vendor cloud provider code. we need to think of a way how to interface this and possibly plan on how to bundle the resulted test suite(s).

some steps to perform here:

• enumerate tests that import cloud provider specifics.
• possibly think of way to interface a generic provider or a generic storage driver or .... etc.
• plan what tests will move and under what structure.
• start moving the tests to a location outside of the framework.
• think of ways how the e2e.test (suite) is going to continue to work and include everything so that we don't break this with the push of button - e.g. compile and run multiple suites but still have the separation in the background.

/area test
/sig testing
/sig cloud-provider
/kind design

/assign @timothysc @andrewsykim
cc @pohly

[neolit123]

/remove-kind failing-test

[oomichi]

/cc @oomichi

[alejandrox1]

/cc @alejandrox1

[andrewsykim]

/assign @stevesloka

[neolit123]

/area e2e-test-framework

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[neolit123]

/lifecycle frozen

[cheftako]

/triage accepted

[cheftako]

cc @jpbetz @cici37 @nckturner @leilajal @jiahuif

[MadhavJivrajani]

/remove-kind design
/kind feature

kind/design will soon be removed from k/k in favor of kind/feature. Relevant discussion can be found here: kubernetes/community#5641

[k8s-triage-robot]

This issue has not been updated in over 1 year, and should be re-triaged.

You can:

• Confirm that this issue is still relevant with /triage accepted (org members only)
• Close this issue with /close

For more details on the triage process, see https://www.kubernetes.dev/docs/guide/issue-triage/

/remove-triage accepted

[k8s-ci-robot]

This issue is currently awaiting triage.

If a SIG or subproject determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[nckturner]

/assign @elmiko