ci: use separate CI jobs for e2e tests

[pmalek]

This PR makes the e2e tests to run in separate jobs, this making the CI faster by parallelizing the tests.

Similar approach has already been done for integration tests:

kubernetes-testing-framework/.github/workflows/tests.yaml

Lines 69 to 86 in cb3a483

	setup-integration-tests:
	runs-on: ubuntu-latest
	outputs:
	test_names: ${{ steps.set_test_names.outputs.test_names }}
	steps:
	- uses: actions/checkout@v3
	- id: set_test_names
	name: Set test names
	working-directory: test/integration/
	# grep magic described in https://unix.stackexchange.com/a/13472
	# sed to add the extra $ is because some of our test names overlap. we need it so the -run regex only matches one test
	run: |
	echo "test_names=$(grep -shoP "(?<=^func )(Test[a-zA-z_0-9]+)(?=\(t \*testing.T\) {)" * | sed -e "s/$/\$/"| jq -R . | jq -cs .)" >> $GITHUB_OUTPUT
	- name: Print test names
	run: echo "Test names ${{ steps.set_test_names.outputs.test_names }}"

[codecov-commenter]

Codecov Report

Patch and project coverage have no change.

Comparison is base (609bf67) 59.70% compared to head (22cd778) 59.70%.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #706   +/-   ##
=======================================
  Coverage   59.70%   59.70%           
=======================================
  Files          43       43           
  Lines        3474     3474           
=======================================
  Hits         2074     2074           
  Misses       1131     1131           
  Partials      269      269           

Flag	Coverage Δ
integration-test	59.70% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.