allow transfer if call is restricted

[ramacarlucho]

Description

Currently in the mono antehandler during the message validation, we check that the CREATE or CALL OP codes are restricted, and the validation fails in case it is.
With the addition of the permissioned evm, the signer of the transaction can be whitelisted an allowed the operation. In the first implementation, the check for a whitelisted address was performed during execution. With this approach we add the check for whitelist address in the antehandler. This requires a small refactor to check the permissions after the msg signature (since we need to know who sends the message)

On base denom transfers
If we restrict the CALL opcode, even the aevmos coin transfer will be restricted. So only cosmos txns will be available, and this is not very useful.
To allow base denom transfers we add the check txdata is empty, to verify that is not a contract call. But this does not cover the case of deposit or fallback. So to prevent this, we simply block all transactions which recipient is a contract.

Closes: EVM-148

---

Author Checklist

All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.

I have...

• tackled an existing issue or discussed with a team member
• left instructions on how to review the changes
• targeted the correct branch (see PR Targeting)

Reviewers Checklist

All items are required.
Please add a note if the item is not applicable
and please add your handle next to the items reviewed
if you only reviewed selected items.

I have...

• added a relevant changelog entry to the Unreleased section in CHANGELOG.md
• confirmed all author checklist items have been addressed
• confirmed that this PR does not change production code
• reviewed content
• tested instructions (if applicable)
• confirmed all CI checks have passed

[GAtom22]

But what about the fallback and receive functions of a contract?
An EOA can trigger a contract call by just sending funds to it.

We could identify this by checking if the to address is a contract, e.g. checking if the address has code

[fedekunze]

this an important point that should be taken into consideration

[fedekunze]

I suggest for contracts checking the method ID from the call data (i.e the first 4 bytes) and comparing it with the receive and fallback bytes

[linear]

EVM-148 Implement the permissioned EVM for the transfers