[Bug]: Solana activity details show incorrect values

[petersnowballls]

Select Topic Area

Question

Body

Describe the bug
Details on Solana activity shows incorrect data in from and to fields when bridging. When checking the the explorer you can see the unknown address to be the first to in the list. The actual address appear a bit down in the list https://explorer.solana.com/tx/2rY5BUciXJFwa4JBypUsy13mJv4kX1pNz5qQ6XKDKHMakRpn2VGRqM4TDwZ8BM9DdRmciauANB2LBYp3qs8rCGYx

Also I wonder why there are 2 TXS

Expected behavior
The from and to address should be the real ones

Screenshots/Recordings
No response

Steps to reproduce
Bridge Mainnet ETH to Solana SOL
once the bridge is done go to Solana account destination and go to activity
There will be 2 TXS
The details don't show the real destination account
Error messages or log output
Detection stage
In beta

Version
12.14.0-beta

Build type
Beta

Browser
Chrome

Operating system
MacOS

Hardware wallet
No response

Additional context
No response

Severity
sev2
Reproduced two transactions when bridging to Solana network. Could it be related to this issue: #30844 ?

During bridging:

the first transaction is the bridge to WSOL
the second transaction is a "settle" from wSOL to SOL
This explorer displays it more clear than the Solana explorer

When bridging AVAX from Avalanche network to SOL on Solana network there are also two receiving transactions for SOL

the first one is a swap from USDC to wSOL: https://solscan.io/tx/3bupEFmTrmDXd6sQdrHdnrMFTRTkDKNWKoFrWPgtmvRhEPNEH6PAJbJMVTxhKSkFf3RvZCFzvuLDMw7FhtqyLTKH
( from AVAX it was swapped to USDC )

the second one is a "settle" from wSOL to SOL:
https://solscan.io/tx/5tfssNiZRBjdkbWkGcEDJ5pzCgoz6zN5m7itXsujVmmmM2TRBLwz8cMZbzSwCx4hYQS4ztRVBP8Wh9XPsM3VLa7G

the activity list in MetaMask shows two receiving transactions for SOL tokens and the amounts don't match with the ones on the explorers

[IRK600]

I believe this is not under swap team, since Send/Receive under Solana is not under Swaps, we believe it's the Solana Snap team.
do not support bridge transactions atm on the keyring-api and wasn't flagged during the bridge implementation.
I will try to get the support for it.