e710bc80 - Only reuse a personal IBAN whose bank still receives

[TaprootFreak]

Incident

Since the EUR personal-IBAN change went to production, customers holding a retired Yapeal EUR
personal IBAN cannot buy by bank transfer at all — they get PersonalIbanIssuanceFailed.

1'678 customers hold such a row.

Cause

getActiveForUserAndCurrency is a findOne with no ORDER BY and no check on whether the bank still
receives. A customer can hold several active rows for one currency — a Yapeal EUR IBAN from 2025 next
to a Frick EUR IBAN issued this week. The query can return the retired one; the caller then sees
virtualIban.bank.receive === false, skips the branch, and falls through.

Until yesterday that fall-through landed on the collection account and nobody noticed. Now the
collection account is deliberately gone, so the same path ends in a 400.

Confirmed on a real account: three active rows (Yapeal EUR receive=false, Yapeal CHF, Frick EUR
receive=true) — the working Frick row was never reached.

Fix

Filter the lookup on bank: { receive: true }. The working row is then found, or none is and issuance
proceeds normally — which is what should have happened for these customers all along.

Scope

One condition in one query, plus the test that pins it. No behaviour change for customers with a
single active IBAN.

getActiveForBuyAndCurrency has the same shape but is unreachable in production today
(asset.personalIbanEnabled and wallet.buySpecificIbanEnabled are off everywhere), so it is left
for the follow-up rather than widening a hotfix.