feat(enakgame): spin as an EnakGame game; remove the old game flow

EnakGame phase 10 of docs/tasks-enakgame.md (EG-1001 to EG-1003).

Spin (EG-1001)
- PROBABILITY entries take an optional label (a wheel segment). The customer game
  list shows a PROBABILITY game's prizes (entry, label, amount, never weights), and
  completing returns the drawn prize, so the client can draw the wheel and stop it
  on the server's draw.
- docs/enakgame-spin.md: the admin steps to set up spin per organization (no
  seeder) and the customer app flow. An HTTP test plays it end to end.

Old game flow removed (EG-1002)
- Routes POST /customer/spin, GET /customer/games, GET /customer/ferris-wheel, and
  admin /marketing/games, /marketing/game-prizes, /marketing/rewards, with their
  handlers, services, processors, repositories, validators, models, contracts,
  mappers and tests (GamePlayProcessor, SpinGameService, rewards, ...). This also
  closes RFC §15 findings 1 and 2 (double charge, spinning another org's game).
- Tables games, game_prizes, game_plays and rewards stay for ledger history.
  entities.StringSlice moves to its own file; the omset tracker (unrouted) keeps
  game_id but no longer embeds the old game response.

games.is_active dropped (EG-1003)
- Migration 000115; nothing reads metadata.coin_cost any more.

The EnakPoint integration docs now point at /customer/enakgame. The Postgres tests
were not run: no test database here. Migration 000115 has not been run anywhere.
The customer app must stop calling the removed endpoints before this is deployed.

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

docs/integration-enakpoint.md

@@ -367,23 +367,18 @@ Kurs per organisasi: `coin_amount` EnakCoin = `point_amount` EnakPoint (default
 
 ## 7. Game
 
-`POST /api/v1/customer/spin` dengan `{ "spin_id": "<id game>" }`. Tanpa PIN.
+Game lama (`POST /api/v1/customer/spin`, `GET /customer/games`,
+`GET /customer/ferris-wheel`, dan admin `/marketing/games`, `/marketing/game-prizes`,
+`/marketing/rewards`) sudah dihapus. Semua game, termasuk spin, sekarang game EnakGame:
 
-Setiap game memotong EnakCoin sebesar `metadata.coin_cost` game itu (default 1).
-Response:
+- Customer: `GET /api/v1/customer/enakgame/games`, lalu
+  `POST /api/v1/customer/enakgame/sessions` (wajib `Idempotency-Key`, memotong
+  `entry_cost` EnakCoin), lalu `POST /api/v1/customer/enakgame/sessions/:id/complete`
+  (server menghitung hadiah EnakCoin). Tanpa PIN.
+- Dashboard: game dan biaya per main (`entry_cost`, bilangan bulat ≥ 1) diatur di
+  `/marketing/enakgame/games`, hadiahnya di reward config.
 
-```json
-{
-  "game_play": { "id": "…", "game_id": "…", "coins_used": 1, "created_at": "…" },
-  "prize_won": { "id": "…", "name": "Voucher 10rb", … },
-  "coins_remaining": 7
-}
-```
-
-EnakCoin kurang, game nonaktif, atau hadiah baru saja habis dijawab `304`; tidak ada
-EnakCoin yang terpotong.
-
-Di dashboard, `metadata.coin_cost` diisi per game dengan bilangan bulat ≥ 1.
+Langkah admin dan alur aplikasi untuk spin ada di [`enakgame-spin.md`](enakgame-spin.md).
 
 ---
 
@@ -549,4 +544,5 @@ Riwayat perubahan: `GET /api/v1/marketing/loyalty-settings/history?page=1&limit=
 **Dashboard**
 - [ ] Tampilkan `point_cashback_percent`, `impact`, `expiry_preview`, dan
       `expiry_activations` sebelum owner menyimpan setting.
-- [ ] Isi `metadata.coin_cost` untuk setiap game.
+- [ ] Buat ulang game (termasuk spin) di `/marketing/enakgame/games` dengan `entry_cost`
+      dan reward config ([`enakgame-spin.md`](enakgame-spin.md)).