fix: accept CAIP-2 EVM network ids in x402-client

[seichris]

Summary

• normalize CAIP-2 EVM network ids like \ to the canonical x402-client aliases before wallet matching and EVM chain lookup
• apply the same normalization in bridge config resolution so CAIP-2 Base quotes work through the existing bridge path as well
• add regression coverage for x402Pay, EVM signing, and bridge config lookup using CAIP-2 ids

Testing

• npm run test --workspace @fastxyz/x402-client
• npm run test

Closes #13

[KcatMa]

Hey @seichris! LGTM. But should it pass the CI? I saw there were two failed checks.

[seichris]

Tracked the CI failure down to the new Base bridge assertions. On GitHub Actions, @fastxyz/allset-sdk 0.1.8 exposes Base mainnet under the AllSet mainnet provider namespace, but x402-client was still resolving Base through the testnet namespace, so getBridgeConfig('base') and getBridgeConfig('eip155:8453') returned null in CI.\n\nPushed a fix to resolve Base through the AllSet mainnet namespace and updated the bridge-context test to match. This should unblock the two failing CI jobs on the next run.

[KcatMa]

LGTM

[KcatMa]

Should we just use something like const chainName = normalizedNetwork or just use normalizedNetwork directly? I think this code will always equal normalizedNetwork

[seichris]

Yes. That mapping was redundant; I removed it and now use normalizedNetwork directly in getBridgeConfig.

[seichris]

Makes sense