fix: skip unrecognized chains/currencies instead of throwing

[badjer]

Summary

• ATXPDestinationMaker.parseDestinationsResponse now skips destinations with unrecognized chains or currencies instead of throwing
• Logs a warning for each skipped destination so issues are visible without crashing
• Ensures server-side chain additions (e.g. tempo) don't break older deployed SDK clients

Context

Adding tempo to the accounts service caused atxp-music (and potentially other services) to crash because the deployed SDK version didn't recognize the chain and threw:

Error: Invalid destination at index 5: chain "tempo" is not a valid chain.

This is a forward-compatibility fix — the SDK should gracefully handle chains it doesn't know about yet.

Test plan

• New test: skips unrecognized chains, returns only valid ones, logs warning
• New test: skips unrecognized currencies, returns only valid ones, logs warning
• New test: still throws on malformed objects (missing fields)
• New test: still throws on invalid amounts
• New test: still throws on invalid response structure
• New test: handles all destinations unrecognized gracefully (empty result)
• New test: valid destinations parse correctly
• New test: non-atxp network returns empty without fetching
• Full atxp-client suite passes (208 tests)

🤖 Generated with Claude Code