perf: thread pre-fetched token to checkRateLimit avoiding re-query

[oyi77]

Problem: getRelayTokenByHash fetches full relay token row. A few lines later checkRateLimit(token.id) does a second SELECT * FROM relay_tokens on a different predicate.

Change:

• checkRateLimit accepts optional existingToken param; skips re-query when provided
• Both relay routes pass the already-fetched token
• Uses RelayToken (camelCase) instead of RelayTokenRow (snake_case) uniformly

Verification: all relay unit tests pass (only pre-existing Cloudflare deploy failures).

[gemini-code-assist]

Warning

You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again!

[diegosouzapw]

Thanks for the perf fix — threading the already-fetched RelayToken into checkRateLimit to skip the redundant SELECT * FROM relay_tokens WHERE id = ? is a real, correct improvement. I verified it behaviorally: the existingToken fast-path and the legacy re-query path return identical allowed/remaining, and the per-minute cap is still enforced correctly (ran a probe unit test against real SQLite, both cases green).

A few things need to happen before this can merge as-is:

1. Scope: this branch also carries an unrelated commit adding 46 provider SVG icons (b6ae243) plus 3 more unrelated "drift" commits (file-size-baseline reformat, a stryker.conf.json test registration, and a codex client-version test bump). None of these are part of the "perf: thread pre-fetched token" change. Could you split them into their own PR(s)? It'll make review and the git history much cleaner, and it'll also unblock this fix faster.

2. Possible unintended regression in the icon commit: b6ae243 removes cohere: "Cohere" from LOBE_PROVIDER_ALIASES in src/shared/components/lobeProviderIcons.ts — that's not mentioned in the commit message (which only lists additions) and looks accidental. Could you confirm whether that removal was intentional?

3. Merge conflicts: config/quality/file-size-baseline.json and tests/unit/provider-models-route-codex.test.ts currently conflict against release/v3.8.47 (that branch has moved since this PR was opened) — a rebase will be needed regardless of the split above.

4. Tests: checkRateLimit in src/lib/db/relayProxies.ts currently has zero test coverage in the repo. Since this PR changes its signature and internal field-mapping (snake_case → camelCase when a token is passed), could you add a unit test asserting the existing-token fast-path agrees with the legacy re-query path and still enforces the rate-limit windows? Happy to share the quick probe test I used for verification if useful.

5. A changelog.d fragment for this fix would also be appreciated per repo convention.

Once split down to just the relay fix + a regression test + changelog fragment, this looks mergeable.

[diegosouzapw]

Merged — reconstructed to just the checkRateLimit pre-fetched-token perf fix (dropped the duplicate 46-icon commit + drift), with a new regression test (3/3, +28/28 related green) + a changelog fragment. Thanks @oyi77! (Remaining red checks are pre-existing release-tip base-reds tracked in #6967.)