test(e2e): descope the stale quickstart suite from the CI job

Its first-ever CI run revealed the quickstart suite predates the
provider bootstrap refactor: it applies only the CatalogEntry, into
root:kedge:providers, while the current flow applies Provider +
CatalogEntry into root:kedge:system:providers and delegates the
APIExport/schemas/bind-grant to `quickstart-provider init` — so every
test from catalog provisioning to tenant enable fails against today's
hub. Modernizing it onto the same bootstrap the infraprovider suite
uses is queued as a follow-up; until then the CI job runs the
infraprovider suite only.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

Author: mjudeikis

.github/workflows/e2e.yaml

@@ -13,23 +13,23 @@ permissions:
 jobs:
   # Subprocess provider suites: hub with embedded kcp + provider binaries as
   # host processes, driven over HTTP + kcp dynamic clients. No kind, no Helm,
-  # no Docker — the cheapest full-kcp coverage we have. The two suites share
-  # the embedded kcp's fixed etcd port (2380), so they run sequentially in
-  # one job rather than as a matrix.
+  # no Docker — the cheapest full-kcp coverage we have.
+  #
+  # NOTE: the older quickstart suite (make e2e-provider) predates the
+  # provider bootstrap refactor (Provider CR + provider-run init) and fails
+  # against the current hub — it is deliberately NOT wired here until it is
+  # modernized onto the same bootstrap the infraprovider suite uses.
   e2e-providers:
     name: Provider suites (embedded kcp subprocesses)
     runs-on: ubuntu-latest
-    timeout-minutes: 45
+    timeout-minutes: 30
     steps:
       - uses: actions/checkout@v4
 
       - uses: actions/setup-go@v5
         with:
           go-version: v1.26.1
 
-      - name: Run quickstart provider e2e
-        run: make e2e-provider
-
       - name: Run infrastructure provider e2e
         run: make e2e-infra-provider