fix: update minimum solana tx version to 1

[mikesposito]

Explanation

The snap calls getTransaction with maxSupportedTransactionVersion: 0. Once v1 transactions start appearing on-chain (today, per the Agave 4.2 rollout), the RPC node returns an error for any getTransaction call that encounters one - it won't just silently skip them.

Concretely, transaction history stops loading for any user whose history includes a v1 tx, or who interacts with a dApp that sends one. The fetchBySignature and fetchAssetsTransactions paths both throw, so the snap's activity feed goes blank or errors out.

References

N/A

Checklist

• I've updated the test suite for new or updated code as appropriate
• I've updated documentation (JSDoc, Markdown, etc.) for new or updated code as appropriate
• I've communicated my changes to consumers by updating changelogs for packages I've changed
• I've introduced breaking changes in this PR and have prepared draft pull requests for clients and consumer packages to resolve them