chore: sync infra OpenAPI specs

[e2b-generated-code-auto-fixer]

This PR syncs OpenAPI specs from e2b-dev/infra:

• spec/openapi.infra.yaml
• spec/openapi.dashboard-api.yaml

It also regenerates dependent TypeScript API types and applies formatting/lint autofixes.

---

This PR was automatically created by the sync-infra-specs workflow.

[claude]

LGTM — mechanical OpenAPI spec sync with auto-generated TypeScript types, no hand-written logic changes.

Extended reasoning...

Overview

This PR is auto-generated by the sync-infra-specs workflow. It updates spec/openapi.infra.yaml and spec/openapi.dashboard-api.yaml to match upstream e2b-dev/infra, and regenerates the corresponding dashboard-api.types.ts / infra-api.types.ts files via openapi-typescript. No hand-written application code is touched. Notable additions: new workspace-admin admin endpoints (project/member/limits CRUD, JWT-authenticated), sandbox fork endpoint, SandboxIam workload identity config, hugepage node metrics, an ApiKeyAuth scheme added to several existing dashboard endpoints, and a new required eventsRetentionExpired/eventsTtlDays field on SandboxRecord/UserTeamLimits.

Security risks

None from this PR's own diff — it only adds type/schema definitions, it does not implement or call any of the new admin endpoints. The new AdminJWTAuth/workspace-admin paths describe a control-plane API that presumably lives in the infra repo; this repo just gains typed bindings for it. Since no route handlers or client calls were added here, there's nothing exploitable yet.

Level of scrutiny

Low. This is a mechanical, tool-generated sync of spec files and their generated TS bindings — the kind of change that's typically safe to fast-track since the generator (openapi-typescript) is deterministic and the source of truth (the infra spec) is external.

Other factors

I checked whether existing consumers (src/core/modules/sandboxes/models.ts, repository.server.ts, src/core/server/api/routers/sandbox.ts) construct object literals of the changed schemas (SandboxRecord, UserTeamLimits) that would break on the new required fields — they only read from these types, so no compile break. A tsc --noEmit pass showed only pre-existing missing-node_modules errors, nothing new tied to the changed files. No bugs were reported by the bug hunting system.