feat(accounts): add account priorities

[cani1989]

fixes #540

Summary

• add account priority levels (gold, silver, bronze) end-to-end across API, DB, proxy selection, and dashboard/account views
• keep priorities behind a settings toggle so the feature can be enabled or disabled without changing account data
• add a per-account priority editor in the accounts page and priority-aware sorting in the dashboard/accounts list

Why

Priority-aware selection makes it possible to prefer certain accounts before falling back to usage/reset-based ordering. The settings toggle keeps the new behavior opt-in, while still letting admins assign and change priorities independently of routing strategy.

Validation

• npm test -- --run src/features/accounts/components/accounts-page.test.tsx
• npm test -- --run src/features/dashboard/components/account-cards.test.tsx src/features/dashboard/components/account-card.test.tsx
• backend integration/unit coverage added for account priority updates, dashboard ordering, settings persistence, and load-balancer selection

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 59cd4febe4

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[Komzpa]

I checked this against a smaller manual account-routing change for the same operator need: #553. There is real overlap in the core routing feature:

• this PR adds per-account gold / silver / bronze priority
• feat(accounts): add manual routing policy #553 uses explicit routing intent: burn_first / normal / preserve
• both approaches select from the manually preferred eligible pool before the normal usage/reset/capacity strategy

The main difference is scope. This PR also includes reset-display/account-list work, quota display appearance settings, Docker/dev-deploy changes, and dashboard sorting. Those may be useful, but they make the routing behavior harder to review as one unit.

For mergeability, I think the account-routing part should be either split into a focused PR, or kept here with a clear OpenSpec delta for the selection contract:

• manual priority applies after hard eligibility gates
• it does not bypass model plan or additional-quota filtering
• preserved/low-priority accounts are fallback-only while other eligible accounts exist

One naming note: UI labels like Burn first, Normal, Preserve may be clearer than medal labels, because “gold” can read as either “best account” or “most valuable account to protect”.