perf(database): index PersonalAccessToken.userId so lookups stop seq-scanning

The two personal-access-token lookups filtered by userId (one also
filtering revokedAt, the other also filtering name) had no index on
userId, so each seq-scanned the whole table to return a single row.
userId is also an unindexed foreign key. Add @@index([userId]); a user
owns few PATs, so the single-column index serves both query shapes
without needing a composite. Migration uses CREATE INDEX CONCURRENTLY
IF NOT EXISTS.

Author: ericallam

.server-changes/index-personal-access-token-user-id.md

@@ -0,0 +1,6 @@
+---
+area: webapp
+type: improvement
+---
+
+Speed up personal access token lookups by indexing them on their owner

internal-packages/database/prisma/migrations/20260812140000_add_personal_access_token_user_id_index/migration.sql

@@ -0,0 +1 @@
+CREATE INDEX CONCURRENTLY IF NOT EXISTS "PersonalAccessToken_userId_idx" ON "public"."PersonalAccessToken"("userId");

internal-packages/database/prisma/schema.prisma

@@ -155,6 +155,8 @@ model PersonalAccessToken {
   updatedAt DateTime @updatedAt
 
   authorizationCodes AuthorizationCode[]
+
+  @@index([userId])
 }
 
 enum OrganizationAccessTokenType {