feat: include recall info in bank tx support responses

[TaprootFreak]

Summary

• Adds recall?: RecallSupportInfo to BankTxSupportInfo, so both the compliance search result and the user-data detail endpoint carry the recall (if any) directly on the bank tx
• Lets the frontend render "Recall exists" state without an extra roundtrip
• RecallService.findByBankTxIds batches the lookup for a whole response; SupportService builds a bankTxId → Recall map and hands it to toBankTxDto

Notes

• RecallSupportInfo exposes id, created, sequence, reason, comment, fee — same fields as RecallListEntry minus the bankTx/checkoutTx/user refs (implicit from context)
• No backend change to the recall creation flow
• Requires the services PR (to be opened) to render the new field

Test plan

• GET /support/userData/:id → bankTxs[i].recall present when a recall exists for that bank tx, absent otherwise
• POST /support/userDataByKey (compliance search) → bankTx[i].recall present / absent accordingly