Ginkgo v2 flag changes break testing older k8s versions

[rifelpet]

kOps uses kubetest2 to test all supported k8s versions. The flag changes from upgrading to ginkgo v2 (#200) impact all usage of kubetest2. Because ginkgo was only upgraded to v2 in k/k's master branch, older k8s versions still use ginkgo v1. This inconsistency results in failures to test older k8s versions.

example with k8s 1.22 from kubernetes/kops#14061

	 -------------------------------------------------------------------
	|                                                                   |
	|  Ginkgo timed out waiting for all parallel nodes to report back!  |
	|                                                                   |
	 -------------------------------------------------------------------

 e2e timed out. path: ./_rundir/d40e3fa1-0f35-11ed-80a5-ea2e797f9e54
[1] flag provided but not defined: -ginkgo.flake-attempts
[1] Usage of /home/prow/go/src/k8s.io/kops/_rundir/d40e3fa1-0f35-11ed-80a5-ea2e797f9e54/e2e.test: 
...

Can we make kubetest2's ginkgo flag changes conditional based on the k8s version being tested? Or what is the expected path forward to use the latest kubetest2 while testing older supported k8s versions?

[BenTheElder]

#201 (comment)

[BenTheElder]

short term: consider pinning the version you use: #17 (comment)

[rifelpet]

Confirmed #206 fixed the issue for kops 👍🏻