🌱 Adopt e2e labels usage

[cahillsf]

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
part of #9620

/area e2e-testing

[k8s-ci-robot]

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

[k8s-ci-robot]

[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 vincepri for approval. For more information see the Code Review Process.

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

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

[cahillsf]

these different methods of filtering get ANDed (https://onsi.github.io/ginkgo/#combining-filters)

[cahillsf]

my idea is to merge this on main, then proceed with the following at each step ensuring the "same" specs/tests are running

not sure if its worth automating? doesn't seems there's a great way to just get the selected specs except using -v --dry-run but that gives.. verbose output, open to ideas here

• follow up with a PR in test-infra that adds the GINKGO_LABEL_FILTER to main e2e testing suites
• remove the "legacy" ginkgo envvar filters in test-infra main e2e testing suites
• migrate k8s::prepareKindestImagesVariablesGingkoFilters logic to k8s::prepareKindestImagesVariables and get rid of the duplicated function in sripts/ci-e2e-lib.sh (and get rid of the corresponding if/else i added in scripts/ci-e2e.sh )
• update the templates in test-infra to reflect the new envvars only