Create e2e tests for ink contracts

[ashneverdawn]

With ink4, contracts can have special e2e tests. These tests test against a running chain (for example using zombienet)

• Allow 3 currencies for smart contracts
• Fund smart contract deployer with various tokens
• Compile erc20 contract with solang, then deploy with swanky (1 pure erc20 token?)
• Deploy ink smart contracts with swanky: (3 different wrapped tokens)
• Call all chain extensions through smart contracts (need special contract to test edge cases not covered by our wrapper contracts?)
• Chain extensions should be thoroughly tested to make sure to not only succeed when supposed to, but also fail when they should.
• Need a test to prove that ERC20 and ink token wrapper contracts are interoperable. Perhaps need to deploy a uniswapv2 clone? or a simple amm. To make sure ink token behaves exactly the same as ERC20 token.

(Needs more info: exact list of tests to create)

[vadaynujra]

@RustNinja please share your estimate or remove yourself from planning poker.

[ashneverdawn]

Closing this ticket, since our wrapper contracts have since been rewritten in Solidity, so we no longer have access to this e2e_test feature of ink4. Instead, we would use the wasm-deploy tool to deploy and call testing contracts, which will already be done as part of pendulum-chain/pendulum-solidity-wrapper#20 for the chain extensions and #225 for Nabla.