evm: add token and NFT bridge interface

[wonge97]

No description provided.

[mizdler]

Hi Wormhole team,
As a project that is built on top of Wormhole Core Bridge and Token Bridge, this PR is what we really needed!
We were looking for an interface for Token Bridge and since there was no interface at the time, we created one.
In our code we are using couple of more public functions from Token Bridge that we hope we could find it in the interface, I leave the interface that we use here so you can consider adding those functions too:
`

function wormhole() external view returns (IWormhole);

function chainId() external view returns (uint16);

function isWrappedAsset(address token) external view returns (bool);

function transferTokens(address token, uint256 amount, uint16 recipientChain, bytes32 recipient, uint256 arbiterFee, uint32 nonce) external payable returns (uint64 sequence);

function wrapAndTransferETH(uint16 recipientChain, bytes32 recipient, uint256 arbiterFee, uint32 nonce) external payable returns (uint64 sequence);

function WETH() external view returns (IWETH);

function finality() external view returns (uint8);

`
If you have questions about the reason that we are using these extra functions I would be happy to answer and discuss.

[evan-gray]

Hi Wormhole team, As a project that is built on top of Wormhole Core Bridge and Token Bridge, this PR is what we really needed! We were looking for an interface for Token Bridge and since there was no interface at the time, we created one. In our code we are using couple of more public functions from Token Bridge that we hope we could find it in the interface, I leave the interface that we use here so you can consider adding those functions too: `

function wormhole() external view returns (IWormhole);

function chainId() external view returns (uint16);

function isWrappedAsset(address token) external view returns (bool);

function transferTokens(address token, uint256 amount, uint16 recipientChain, bytes32 recipient, uint256 arbiterFee, uint32 nonce) external payable returns (uint64 sequence);

function wrapAndTransferETH(uint16 recipientChain, bytes32 recipient, uint256 arbiterFee, uint32 nonce) external payable returns (uint64 sequence);

function WETH() external view returns (IWETH);

function finality() external view returns (uint8);

` If you have questions about the reason that we are using these extra functions I would be happy to answer and discuss.

Thanks for this insight! Will leave a comment to ensure it gets added.

[evan-gray]

Let’s review once more and ensure this is the cleanest interface and includes the latest updates like finality. My work on fast transfer needed the structs too, so making that easily available would likely be beneficial as well.

[gator-boi]

Closing in favor of #1710