feat(loyalty): remove paying with EnakPoint

EnakPoint can only be redeemed for vouchers now: it can no longer pay for
orders and is never cashed out (docs/enakgame-prd.md §3.2, EG-001,
EG-002). No order was ever paid with EnakPoint, so there is no data to
move.

Removed:
- POST /customer/wallet/payment-code, POST /customer/orders/:id/pay-with-points
  and GET /orders/:id/point-payment/preview, with their processors,
  repositories, services, handlers and tests.
- The point payment method type: paying, splitting and refunding with it,
  the outlet filter on the method list, and the system-method guard.
- points and payment_code on CreatePayment; points_used and point_value
  on payments; accepts_point_payment on the customer outlets.
- The outlet point_payment settings. A PUT that still sends them is
  rejected as an unknown field.
- The EnakPoint split in the payment method analytics.
- PAYMENT and PAYMENT_REFUND from the wallet type rules. Tests that used
  them as a generic EnakPoint debit use REWARD_REDEEM.
- The EnakPoint-paid part from the earning basis, which is
  subtotal − discount again.

Migration 000102 drops the trigger, the point methods and their index,
the payments columns, and the outlet settings, and restores the method
type CHECK without point. payments.payment_method_id is ON DELETE
RESTRICT, so it fails rather than lose a payment made with EnakPoint.

The integration docs list the removed endpoints and fields, and the
EnakPoint & EnakCoin PRD and tasks note what is superseded.

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

internal/models/analytics.go

@@ -33,14 +33,7 @@ type PaymentMethodAnalyticsResponse struct {
 
 // PaymentMethodSummary represents the summary of payment method analytics
 type PaymentMethodSummary struct {
-	// Money actually received. EnakPoint is not money in (docs/prd-point-coin.md F9,
-	// K7) and is reported apart; its accounting treatment waits on note N2.
-	TotalAmount float64 `json:"total_amount"`
-	// Rupiah paid with EnakPoint, and how many EnakPoint that was.
-	PointAmount float64 `json:"point_amount"`
-	PointsUsed  int64   `json:"points_used"`
-	// TotalAmount plus PointAmount: the value of the orders paid.
-	TotalWithPoints   float64 `json:"total_with_points"`
+	TotalAmount       float64 `json:"total_amount"`
 	TotalOrders       int64   `json:"total_orders"`
 	TotalPayments     int64   `json:"total_payments"`
 	AverageOrderValue float64 `json:"average_order_value"`
@@ -54,11 +47,7 @@ type PaymentMethodAnalyticsData struct {
 	TotalAmount       float64   `json:"total_amount"`
 	OrderCount        int64     `json:"order_count"`
 	PaymentCount      int64     `json:"payment_count"`
-	// Share of the money received; 0 for EnakPoint, which is not money in.
-	Percentage float64 `json:"percentage"`
-	PointsUsed int64   `json:"points_used"`
-	// False for EnakPoint.
-	CountsAsCashIn bool `json:"counts_as_cash_in"`
+	Percentage        float64   `json:"percentage"`
 }
 
 // SalesAnalyticsRequest represents the request for sales analytics