fix(paysafe): vault recurring wallet handle after CIT

[shuklatushar226]

Summary

• settle recurring Apple Pay / Google Pay CITs with the account-bound SINGLE_USE handle
• convert the spent handle to a validated PAYABLE/MULTI_USE handle after a successful CIT
• persist the initial transaction, wallet account hint, and stored-credential type in mandate metadata for MIT
• keep backward compatibility with the compact mandate reference emitted by older UCS versions

Why

Paysafe differs from other recurring-wallet connectors: the raw wallet token creates a SINGLE_USE payment handle, and the reusable customer-vault handle must be created with a second paymentHandleTokenFrom call. Sending an explicit account ID while settling the original wallet handle is rejected by Paysafe; the later MIT must use the account that processed the initial transaction.

Verification

• Apple Pay CIT -> MULTI_USE conversion -> MIT succeeded locally through Hyperswitch
• Google Pay CIT -> MULTI_USE conversion -> MIT succeeded locally through Hyperswitch
• cargo +nightly fmt --all -- --check
• cargo check -p grpc-server
• no test code added

Related

• Hyperswitch: feat(paysafe): support Apple Pay / Google Pay recurring (CIT→MIT) hyperswitch#13410
• Original UCS recurring-wallet support: feat(paysafe): Apple Pay / Google Pay recurring + encrypted GPay passthrough #1986