Run `e2e-conformance` test against multiple Kubernetes version to ensure compatibility

[ArkaSaha30]

What would you like to be added?

Limitation

The current build-test-lint.yml GitHub Actions workflow executes test-e2e-conformance-virtual-k8s-cluster-ci against a single fixed Kubernetes cluster version(currently only k8s v1.32.0).

Enhancement

CLUSTER_VERSION environment variable as a part of hack/run-e2e-conformance-virtual-cluster.sh can be configured to pass a specific Kubernetes version.

By leveraging this CLUSTER_VERSION environment variable we can implement a job matrix in GitHub Actions to run conformance test against multiple Kubernetes versions.

The scope of supported Kubernetes minor versions support for a particular sriov-network-device-plugin release can be deliberated and determined through this issue.

What is the use case for this feature / enhancement?

• Ensure broader compatibility of the sriov-network-device-plugin across multiple Kubernetes versions.
• Publish a compatibility matrix between sriov plugin version and Kubernetes version for users

[zeeke]

+1 from side. I'd put the last 3 k8s releases in the matrix, and it would be nivce to find somehow an auto updater for it

[SchSeba]

It's a nice Idea the problem here is that we don't have capacity to run many versions on every PR specially not in parallel.
we only have 2 servers for all the sriov related projects