Consider running e2e GDK tests in gitlab-renovate-forks/gitlab
There was a broken master because an MR in https://gitlab.com/gitlab-renovate-forks/gitlab didn't automatically run the e2e tests on GDK because that project is a fork and it probably doesn't have the QA_RUN_TESTS_ON_GDK
variable that the test pipeline requires. See gitlab-org/quality/engineering-productivity/master-broken-incidents#4583 (comment 1685460302)
We should decide if we want to run the GDK tests in that fork. And if so, should it be only that fork, or all forks?
We should also decide if we want to make it the default to run the GDK tests, perhaps with the option to not run them (e.g., by adding QA_RUN_TESTS_ON_GDK=false
)