feat(loyalty): report EnakPoint apart from money received

Keeps EnakPoint out of the money in on the payment method analytics
(docs/prd-point-coin.md F9, K7, PC-308), the one report that sums payments;
the daily transaction and profit-loss PDFs do not break payments down by
method.

summary.total_amount is now only money actually received. EnakPoint stays
listed as its own method, with points_used, and the summary adds
point_amount, points_used and total_with_points. Each method row says
whether it counts_as_cash_in, and the shares are of the money received, 0
for EnakPoint. The average order value still includes what EnakPoint paid,
since that is part of what the orders were worth. How EnakPoint is booked
waits on note N2.

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

internal/transformer/analytics_transformer.go

@@ -60,6 +60,8 @@ func PaymentMethodAnalyticsModelToContract(resp *models.PaymentMethodAnalyticsRe
 			OrderCount:        item.OrderCount,
 			PaymentCount:      item.PaymentCount,
 			Percentage:        item.Percentage,
+			PointsUsed:        item.PointsUsed,
+			CountsAsCashIn:    item.CountsAsCashIn,
 		})
 	}
 
@@ -72,6 +74,9 @@ func PaymentMethodAnalyticsModelToContract(resp *models.PaymentMethodAnalyticsRe
 		GroupBy:        resp.GroupBy,
 		Summary: contract.PaymentMethodSummary{
 			TotalAmount:       resp.Summary.TotalAmount,
+			PointAmount:       resp.Summary.PointAmount,
+			PointsUsed:        resp.Summary.PointsUsed,
+			TotalWithPoints:   resp.Summary.TotalWithPoints,
 			TotalOrders:       resp.Summary.TotalOrders,
 			TotalPayments:     resp.Summary.TotalPayments,
 			AverageOrderValue: resp.Summary.AverageOrderValue,
@@ -617,6 +622,8 @@ func DashboardAnalyticsModelToContract(resp *models.DashboardAnalyticsResponse)
 			OrderCount:        item.OrderCount,
 			PaymentCount:      item.PaymentCount,
 			Percentage:        item.Percentage,
+			PointsUsed:        item.PointsUsed,
+			CountsAsCashIn:    item.CountsAsCashIn,
 		})
 	}