fix(quota): route remaining console quota reads through the connection proxy

[maxmad64bis]

Stacked on #15885. Only the last commit is this PR's; I'll rebase once it lands.

⚠️ base-red inherited: #15306

Summary

Quota reads for nine providers leave the direct address while the same connection's requests use its assigned proxy. This change routes those nine readers through the connection proxy, so a reading with a proxy assigned leaves by the proxy and a reading without one still fetches directly. The provider limits screen shows the same data over the new network path — it's the same reading by proxy.

Related Issues

• Related to fix(quota): route quota fetcher reads through the connection proxy #15885

Target Branch

• Base is the active release/v3.8.x branch (the highest open release/v*), not main
• New feature? From 3.8.55 on it is held with the v4-feature label for the v4 channel

Validation

• Change type: routing
• Focused tests and category gates from the golden path
• npm run lint
• Reconciled with the current active release base; focused checks rerun afterward
• Production-code changes include a new or updated automated test in this PR

Tests Added Or Updated

• tests/unit/quota-fetchers-connection-proxy.test.ts — nine per-provider tests, one per remaining reader, plus a shared no-auth invalidation test and a static guard that fails naming any reader that calls fetch outside the helper.

Coverage Notes

• open-sse/services/jinaQuotaFetcher.ts — covered by jina quota reads inside the proxy context.
• open-sse/services/llmgatewayQuotaFetcher.ts — covered by llmgateway quota reads inside the proxy context.
• open-sse/services/lyceumQuotaFetcher.ts — covered by lyceum quota reads inside the proxy context.
• open-sse/services/moonshotQuotaFetcher.ts — covered by moonshot quota reads inside the proxy context.
• open-sse/services/newApiAggregatorQuotaFetcher.ts — covered by new-api aggregator quota reads inside the proxy context.
• open-sse/services/opencodeQuotaFetcher.ts — covered by opencode quota reads inside the proxy context and opencode quota invalidation clears the shared no-auth reading.
• open-sse/services/openrouterQuotaFetcher.ts — covered by openrouter quota reads inside the proxy context.
• open-sse/services/tavilyQuotaFetcher.ts — covered by tavily quota reads inside the proxy context.
• open-sse/services/v0QuotaFetcher.ts — covered by v0 quota reads inside the proxy context.

Reviewer Notes

• Merge: lands after fix(quota): route quota fetcher reads through the connection proxy #15885 — it shares the helper file only.
• Behavior: with a proxy assigned, quota reads for these nine providers now leave by the proxy instead of the direct address, and without one the direct fetch is unchanged. opencode reads without a stored identifier use the shared no-auth fallback instead of reporting an unknown reading.