feat(cities): cities are a tree again, as legacy's; old dashboard permissions merged (PERS-02, PERM-01)

Cities (owner: as legacy)
- City.parentId (self relation) replaces the flat `province` label; the
  migration turns each label into a parent row («استان …») first, so nothing
  is lost.
- Admin pickers are legacy's tree (CityTreeSelect): the top level, the
  country, is a heading. The city form and grid get «والد».
- Restored legacy _getP: a city without its own percent takes its
  ancestor's. Restored the omde-customer form's city → percent autofill.
- Import copies legacy parents; delete refuses a city with children; a
  parent loop is refused.

Permissions (owner approved the deletion)
- dashboard / dashboard.omde / dashboard.tak rows become dashboard.view,
  then are deleted.
- Import maps them the same way: legacy types 102, 104, 105, 108 and 135
  had lost the dashboard.

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

apps/api/prisma/migrations/20261008160000_dashboard_permission_merge/migration.sql

@@ -0,0 +1,14 @@
+-- PERM-01 (owner approval 2026-10-08): legacy's two dashboard permissions
+-- «آمار عمده فروشی» (dashboard.omde) and «آمار تک فروشی» (dashboard.tak), and
+-- their tree parent "dashboard", became the single "dashboard.view" when the two
+-- dashboards became one. A database seeded before that change still holds the
+-- old rows: nothing reads them and the permission screen cannot show or revoke
+-- them. Whoever held one keeps the dashboard through "dashboard.view", then the
+-- old rows go. Data only, idempotent.
+INSERT INTO "permission" ("rid", "userTypeId")
+SELECT DISTINCT 'dashboard.view', "userTypeId"
+FROM "permission"
+WHERE "rid" IN ('dashboard', 'dashboard.omde', 'dashboard.tak')
+ON CONFLICT DO NOTHING;
+
+DELETE FROM "permission" WHERE "rid" IN ('dashboard', 'dashboard.omde', 'dashboard.tak');

apps/api/prisma/migrations/20261008170000_city_tree/migration.sql

@@ -0,0 +1,33 @@
+-- PERS-02 (owner approval 2026-10-08): cities become a tree again, as in legacy
+-- (country > province > city > district, henza `cities.parent`). The flat
+-- `province` label is turned into parent rows, nothing is lost, then dropped.
+
+ALTER TABLE "City" ADD COLUMN "parentId" TEXT;
+
+-- One province row per distinct label, named as legacy names them
+-- («استان تهران»), unless a city row already carries that name.
+INSERT INTO "City" ("id", "name")
+SELECT 'cprov' || substr(md5(p.pname), 1, 20), p.pname
+FROM (
+  SELECT DISTINCT
+    CASE WHEN btrim("province") LIKE 'استان%' THEN btrim("province") ELSE 'استان ' || btrim("province") END AS pname
+  FROM "City"
+  WHERE "province" IS NOT NULL AND btrim("province") <> ''
+) p
+WHERE NOT EXISTS (SELECT 1 FROM "City" c WHERE c."name" = p.pname);
+
+UPDATE "City" c
+SET "parentId" = (
+  SELECT p."id" FROM "City" p
+  WHERE p."id" <> c."id"
+    AND p."name" = CASE WHEN btrim(c."province") LIKE 'استان%' THEN btrim(c."province") ELSE 'استان ' || btrim(c."province") END
+  ORDER BY p."id"
+  LIMIT 1
+)
+WHERE c."province" IS NOT NULL AND btrim(c."province") <> '';
+
+ALTER TABLE "City" DROP COLUMN "province";
+
+CREATE INDEX "City_parentId_idx" ON "City"("parentId");
+
+ALTER TABLE "City" ADD CONSTRAINT "City_parentId_fkey" FOREIGN KEY ("parentId") REFERENCES "City"("id") ON DELETE RESTRICT ON UPDATE CASCADE;