feat(pricing): the server prices app orders with legacy's making-charge formula (MON-08)

Legacy: final % = variant % + customer % − the largest active promotion
on the product, its category or its brand; rial charge 0. The apps sent
the variant's own % only, so the new app undercharged by the customer's
percent (usually 3) and ignored promotions, and the server trusted
whatever the app sent.

- pricing/wage-formula.ts: one formula, legacy by default, with
  coefficients, promotion pick, constant, floor/cap and rounding so the
  admin screen can change it; validated
- an app order is priced by it; the app's wage, discount and rial charge
  are ignored; an operator's manual numbers are kept
- POST customer/me/wage-quote; both apps show that figure
- admin/pricing/wage-formula (config.wage): read, preview, approve with
  the sample it was checked on, last 20 versions kept; the setting is
  kept off the generic const routes

Owner approval: 2026-10-08.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

apps/api/prisma/migrations/20261008150000_wage_formula_permission/migration.sql

@@ -0,0 +1,9 @@
+-- «اجرت» admin screen (owner ruling 2026-10-08): its permission for the
+-- seeded super-admin user type. A fresh seed grants every rid in ALL_RIDS;
+-- an existing database gets the new one here. Data only, idempotent.
+-- The formula itself needs no row: until an admin approves one, the server
+-- uses legacy's formula (pricing/wage-formula.ts LEGACY_WAGE_FORMULA).
+INSERT INTO "permission" ("rid", "userTypeId")
+SELECT 'config.wage', 85
+WHERE EXISTS (SELECT 1 FROM "user_type" WHERE "id" = 85)
+ON CONFLICT DO NOTHING;