Use API discovery for E2E store cleanup

[alfonso-noriega]

WHY are these changes introduced?

Fixes #0000

E2E cleanup can leak development stores when per-test teardown skips store deletion because apps are still installed. The final cleanup job was also discovering stores by scrolling and scraping the Dev Dashboard UI, which has been observed loading hundreds/thousands of rows while finding zero current-run stores.

WHAT is this pull request doing?

• Primes cleanup auth for both CLI Business Platform requests and Playwright browser state.
• Discovers matching app development stores through Business Platform GraphQL before falling back to Dev Dashboard UI scraping.
• Runs final current-run app cleanup before current-run store cleanup so stores are more likely to be empty when deletion runs.

No changeset: this is internal CI/E2E maintenance only.

How to test your changes?

• pnpm nx run e2e:type-check --skip-nx-cache
• pnpm nx run e2e:lint --skip-nx-cache
• pnpm nx run cli:build --skip-nx-cache
• pnpm --filter e2e exec tsx --eval "Promise.all([import('./scripts/cleanup-stores.ts'), import('./scripts/prime-browser-auth.ts')]).then(() => console.log('script imports ok'))"

Post-release steps

None.

Checklist

• I've considered possible cross-platform impacts (Mac, Linux, Windows)
• I've considered possible documentation changes
• I've considered analytics changes to measure impact
• The change is user-facing — I've identified the correct bump type (patch for bug fixes · minor for new features · major for breaking changes) and added a changeset with pnpm changeset add (not applicable: internal CI cleanup)

[alfonso-noriega]

• Use API discovery for E2E store cleanup #8053 👈 (View in Graphite)
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.