Dev impersonation requires pre-seeded accounts — create unknown names on demand

**Status: enhancement**

## Current behavior
`POST /api/auth/dev/impersonate` (development-only) 404s when the requested `steamName` has no existing `players` row. Local multi-client testing therefore requires a seeding step first (e.g. `seed-speedrun-players.ts`) before any account can be impersonated.

## Proposal
On a `steamName` miss, create the player row on the fly (ToS pre-accepted so throwaway accounts skip the prompt) and log in as it — making local testing zero-setup: launch two clients, impersonate any two names, play. `playerId` (uuid) misses should still 404, since creating a row for a specific uuid is meaningless. The endpoint is already gated to `NODE_ENV=development`, so production exposure is unchanged.

Search for the POST /api/auth/dev/impersonate handler and its player lookup, then inspect seed-speedrun-players.ts for the player fields and login behavior. Done means an unknown steamName is created with ToS pre-accepted and logged in, while a missing playerId still returns 404; verify both paths through the development endpoint.

Vom Indexierungsmodell aus dem Issue-Text verfasst.