[Bug]: Send ERC-6909 - I am able to initiate Send ERC-6909 (currently not supported) by starting a regular Send and then selecting the ERC-6909 token leading to a `safeTransferFrom` call (not in the standard)

Describe the bug

I am able to import ERC-6909 tokens in the wallet, and when I try to initiate a Send, the Send button is disabled with the message Sending of ERC-1155 NFT assets is not yet supported -- this should be updated.

However, I am able to start a regular Send ETH, and then select the ERC-6909 asset, and proceed to the last confirmation screen. There I see that a safeTransferFrom contract call is created instead of a transferFrom.

The ERC-6909 Minimal Multi-Token Interface standard doesn't support the safeTransferFrom method.

See more in the spec here.

Expected behavior

Either we don't allow to perform Sends of ERC-6909 tokens, so then we should:

• Block the UI when we change the token once a Send has been initiated
• Update the Info ticker with the appropiate token standard

Or if we do, then we should call the appropriate transferFrom function when performing a Send.

Screenshots/Recordings

https://github.com/user-attachments/assets/e935a6a8-f101-43a4-a19e-2802c19d4a83

Steps to reproduce

1. Go to remix
2. Create a new file token.sol
3. Paste an ERC6909 contract code (you can use this one)
4. Connect MM
5. Deploy the token contract
6. Mint some tokens
7. Import them into the wallet
8. Start a send ERC6909
9. See button is disabled, and info picker
10. Cancel the flow
11. Start a Send ETH
12. Change the asset to ERC6909
13. Go to last confirmation screen
14. See a confirmations is created with safeTransferFrom method.

Error messages or log output

Detection stage

In production (default)

Version

12.9.3

Build type

None

Browser

Chrome

Operating system

Linux

Start by reproducing the send flow described in steps 7–14, then read the ERC-6909 specification linked in the issue. Trace asset selection from a regular Send through the final confirmation screen; done means ERC-6909 sends are either blocked with the correct standard-specific messaging or use the standard's transferFrom call.