feat(payments): wallet screen with balances, benefits and storefront

Add the "Кошелёк" section to the settings hub: context-visible chip
balances, active benefits (no-ads term/forever, hints) and a storefront of
chip-priced values and money-priced chip packs. Guests have no wallet; the
Google Play build hides the money purchases behind a RuStore stub; a web
purchase that would draw VK/Telegram chips warns first.

Add the catalog read path the storefront needs — a context-projected
GET /api/v1/user/wallet/catalog (payments service + store, gateway op
wallet.catalog, FBS Catalog/CatalogProduct/CatalogAtom, client decode) —
plus the client leg for the existing wallet.get/buy ops. Value spends reuse
the existing spend path; the chip-pack purchase (money order flow) arrives
with payment intake, so its action is a disabled placeholder for now.

Covered by Go unit (catalog projection) + integration (/wallet/catalog over
Postgres), vitest (formatting, spendable selection, web-spend warning, GP
flag, codec + gateway encode round-trips) and Playwright mock e2e (render,
guest-hidden, GP stub, warning) on Chromium + WebKit.

ui/scripts/bundle-size.mjs

@@ -26,10 +26,11 @@ const DIST = 'dist';
 // countdown toast live in the always-loaded game screen (Game.svelte) — and to 120 for the offline
 // pass-and-play (hotseat) mode: the on-screen PIN pad, the creation roster and the in-game host menu
 // live in the always-loaded New Game / Game / Lobby screens (the offline engine and the tiny PIN
-// hashing stay in lazy chunks / are negligible). The heavy parts — the dict loader, the move
-// generator and the preload orchestration — still stay in lazy chunks. Scoped CSS lands in the CSS
-// chunk, not this JS budget.
-const BUDGET = { app: 120, shared: 30, landing: 5 };
+// hashing stay in lazy chunks / are negligible), then to 123 for the Wallet section — its screen,
+// storefront logic and the catalog codec load with the always-mounted settings hub (its i18n lands
+// in the shared chunk). The heavy parts — the dict loader, the move generator and the preload
+// orchestration — still stay in lazy chunks. Scoped CSS lands in the CSS chunk, not this JS budget.
+const BUDGET = { app: 123, shared: 30, landing: 5 };
 
 // gzipped returns the gzipped byte size of a built asset, or 0 when the reference is not a
 // local file (e.g. the Telegram SDK loaded from a CDN) or is missing.