feat: P9 #4 — 출금 가용한도를 환수채권 상계 후 실지급액(payable_amount)으로 전환

P9에서 산출하던 payable_amount(=환수 상계 후 실지급액)가 출금 한도에 미반영
(cosmetic)이던 것을 연결. 이제 환수채권 회수가 모바일 출금 가용액을 정확히 줄인다.

- V112: 기존 settle_master.payable_amount 백필 = GREATEST(net_amount,0)
  (V111에서 DEFAULT 0 추가됨 → 구 데이터 보정. clawback 무활동 행만 대상=멱등).
- core: SettleMasterMapper.xml cols에 clawback_recovered/carryover/payable_amount 추가,
  SettleMasterResp 3필드 노출.
- api: MobileMeService.withdrawableBalance 한도 산정을 net→payable_amount 기준으로
  (payable null이면 max(net,0) 폴백). WithdrawableBalance DTO에 payableAmount 추가,
  remainingAmount = payable − used. createWithdrawRequest 가드도 자동 반영.
- PWA: withdraw.ts 타입 + WithdrawCreate 드롭다운/카드를 '실지급가능(payable)' 표기로.

검증: ./gradlew build(test포함) SUCCESSFUL, PWA tsc 0오류. Flyway V112 적용(schema v112).
백필 150/150 행 payable==max(net,0). 라이브 agent01 withdrawable-balance가 payableAmount
노출 + remaining=payable−used(13492−151000=-137508) 정확.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

ga-core/src/main/java/com/ga/core/vo/settle/SettleMasterResp.java

@@ -22,6 +22,9 @@ public class SettleMasterResp {
     private BigDecimal grossAmount;
     private BigDecimal taxAmount;
     private BigDecimal netAmount;
+    private BigDecimal clawbackRecovered;   // V111: 당월 환수채권 상계 회수액
+    private BigDecimal clawbackCarryover;   // V111: 당월 발생→이월된 미수액
+    private BigDecimal payableAmount;        // V111: 실지급(이체대상) = max(0,net) − recovered
     private String status;
     private String statusName;
     private LocalDateTime calcDate;

ga-core/src/main/resources/mapper/settle/SettleMasterMapper.xml

@@ -11,6 +11,7 @@
         s.settle_month, s.recruit_total, s.maintain_total,
         s.exception_plus, s.exception_minus, s.override_total, s.chargeback_total,
         s.gross_amount, s.tax_amount, s.net_amount,
+        s.clawback_recovered, s.clawback_carryover, s.payable_amount,
         s.status,
         (SELECT cc.code_name FROM common_code cc WHERE cc.group_code='SETTLE_STATUS' AND cc.code=s.status) AS status_name,
         s.calc_date, s.confirmed_by, u.user_name AS confirmed_by_name,