Wrong function type when sending ETH

[estebanmino]

Describe the bug

When sending an ETH transaction with hex data, Function Type is CONTRACT INTERACTION even though I'm not interacting with a contract.

To Reproduce
Steps to reproduce the behavior:

Follow the GIF

Expected behavior
Should have the same behavior, regarding Function Type, when sending ETH without hex data.

Screenshots
If applicable, add screenshots to help explain your problem.

Browser details (please complete the following information):

• OS: Ubuntu
• Browser Chrome
• MetaMask Version 5.3.0

Additional context
Add any other context about the problem here.

[bdresser]

If a normal send has hex data attached, it's very tough for us to distinguish it from a contract interaction. @alextsg this has come up before, yes?

[alextsg]

@bdresser We can make an external request to check if the recipient is a smart contract address, which is what we're doing in the transactions view. I can make that change here as well.