feat: dualVMToken starknet functions

[obatirou]

Time spent on this PR:

Pull request type

Please check the type of change your PR introduces:

• Bugfix
• Feature
• Code style update (formatting, renaming)
• Refactoring (no functional changes, no api changes)
• Build related changes
• Documentation content changes
• Other (please describe):

What is the current behavior?

Resolves #1417

What is the new behavior?

• add tests
• interact directly with starknet address with DualVMToken

---

This change is 

[ClementWalter]

So tl;dr after irl comments

• use overloading and decided if it's starknet or EVM based on type: address <> EVM and uint256 <> Starknet
• update the _wrap_kakarot util to use function selector instead of function name
• make the get_function_by_identifier return a _wrap_kakarot function such that it's possible to use contract.get_function_by_identifier("transferFrom(uint256,address,uint256)")(0xabde1_sn, 0xabde1_evm, 1234)

Relevant utils may include
from web3._utils.abi import abi_to_signature
from eth_utils import function_abi_to_4byte_selector

[ClementWalter]

@obatirou see

so we can add functions to the dict and access them easily in the test

Overloading function signatures

[ClementWalter]

about DEFAULT_PRIME : you test that you give an invalid starknet address, ie an address greater or equal than DEFAULT_PRIME. You could parametrize over [DEFAULT_PRIME, 2**256), but if it's only one value, I think that DEFAULT_PRIME makes it more explicit