bug: Vercel integration env var import is capped at ~25 variables (first API page only)

[isshaddad]

Provide environment information

n/a

Describe the bug

When importing environment variables from Vercel via the Vercel integration, only ~25 variables are offered for import even when the Vercel project has more configured. Expected: all (non-secret-type) variables from the Vercel project are available to import.

Cause: getVercelEnvironmentVariables (apps/webapp/app/models/vercelIntegration.server.ts:445-474) calls client.projects.filterProjectEnvs() and only uses the first page of the response. Vercel's GET /v10/projects/{idOrName}/env endpoint has no limit request parameter — pagination is response-driven via pagination.next — and the code detects the extra pages but only logs a warning instead of fetching them:

// line 467
logger.warn(
  "Vercel filterProjectEnvs returned paginated response - some env vars may be missing",
  ...
)

Reproduction repo

n/a

To reproduce

n/a

Additional information

1. Create a Vercel project with 30+ environment variables (non secret-type).
2. Connect the project to Trigger.dev via the Vercel integration.
3. Open the env var import step/sync.
4. Only the first ~25 variables are listed; the rest are silently missing. Server logs show the filterProjectEnvs returned paginated response warning.

[Atharva-026]

Hey! I came across this issue and would love to fix it. The root cause is clear — getVercelEnvironmentVariables only reads the first page and logs a warning instead of following pagination.next. I'll replace that with a loop that fetches all pages. Will have a PR up soon!