[WalletConnect] Cross-Chain swap to an incorrect address

It seems that the issue related not switching addresses when changing chains runs much deeper, and the logic for handling different chains does not account for the possibility that different chains might have different addresses.

Steps to Reproduce:

1. Connect a wallet via WalletConnect that uses different addresses for different chains, such as https://coin.space/wallet/

WalletConnect approved session namespace:

{
    "eip155": {
        "chains": [
            "eip155:1",
            "eip155:42161",
            "eip155:10"
        ],
       // ...
        "accounts": [
            "eip155:1:0xB6bB59b3aC844e8e4A98A281D57E3E0628bcb471",
            "eip155:42161:0xAd8eDE8697aF92AF31Fe66EDAD9A52A74F74464E",
            "eip155:10:0x0CFfE8EF251B2C8Ee2481F0142b531715877D417"
        ]
    }
}

2. Initiate a swap (in my case, OP ETH to ARB ETH).

4. Confirm the swap.

Expected Behavior

ARB ETH should be sent to the correct address.

Actual Behavior

ARB ETH was sent to the same address as OP ETH, but on the ARB chain.

• https://optimistic.etherscan.io/tx/0x549bfcc3c056370563dee07a2d279470bfc3f6d5caa0ae2d99686e5517573c84
• https://arbiscan.io/tx/0xd5ab1c471ab6b519553429b57a24db6c7f9d4f5eea03f2fbb78e93099eefc6e0
• https://arbiscan.io/address/0x0CFfE8EF251B2C8Ee2481F0142b531715877D417#internaltx

Start with the WalletConnect approved session namespace and the swap confirmation flow described in the reproduction steps, then compare the chain-specific accounts for Optimism and Arbitrum. Use the linked Optimistic Etherscan and Arbiscan transactions to verify the recipient selection. Done means the destination chain receives the swap at that chain's correct address.