[BUG}: Long address EVM cryptotranfer

**Description**

The EVM address is 0x2844e0b3ebfd0e7b5843c27f61a14d4533eb2b90
The account Id is 0.0.5465490
The solidity equivalent of 0.0.5465490 is 0x0000000000000000000000000000000000536592

Using ethers.js and composing a transaction to send to the EVM address, all is well.

If I try to send to the long zero address, the tx fails with insufficient gas, increasing gas to 200,000 was still insufficient.
I can send to either of the 3 using the native api calls in the SDK.

If I am using MetaMask or Brave Wallet or whatever, and I transfer to a legitimate user account some Hbar, it should work.

Additional context

if an account has an alias which is an EVM address the long zero address cannot be used for transfers. If the account does not have an alias that looks like an EVM address then the long zero address can be used.

This is incorrect, if alias set both adresses sould be able to receive hbar. Mainnet fails too,

Hedera network
testnet
Version
v0.58

Operating system
None

Start by reproducing the transfer with ethers.js using the long zero address on the Hedera testnet, then compare it with the native SDK calls and the account's EVM alias. Done means both the EVM address and its long zero-address form can receive HBAR when the alias is present, without requiring excessive gas.

Written by the indexing model from the issue text.