breaks money

Solana adapter's payment scan throws when any candidate is a version 1 transaction

src/adapters/solana.ts (line 394) loops over the destination's signatures and calls connection.getTransaction(sig, { maxSupportedTransactionVersion: 0 }) for each. When any of them is a version 1 transaction, @solana/web3.js throws "Transaction version (1) is not supported by the requesting client", which ends the whole scan, so a payment can be missed because of an unrelated v1 transaction to the same address.

Version 1 transactions are a large share of mainnet now (about 40% of non-vote transactions in a block I sampled; 115 of 332 in another), so this depends only on which wallet or SDK built the transaction.

• src/adapters/solana.ts:394

getTransaction(<v1 signature>, { maxSupportedTransactionVersion: 0 })  -> error -32015 "Transaction version (1) is not supported by the requesting client"
getTransaction(<v1 signature>, { maxSupportedTransactionVersion: 1 })  -> the transaction (version 1, meta present)

Fix: maxSupportedTransactionVersion: 1. @solana/web3.js 1.99.0 or later parses v1 fine with it (tested); 1.98.x rejects a version 1 answer even when asked, so it needs the bump too.