test(e2e): add a test to deploy contracts

[lumtis]

Description

Add a entry in zetae2e allowing to deploy smart contracts used in some tests in the E2E tests (right now test_dapp on zevm and evm)

Decided to add it as a "test" with the run command, so we can use it without any changes in our current CI.

Usage:

zetae2e run deploy:[contract_name] --config [config]

Example:

zetae2e run deploy:testdapp_zevm --config bsc_config.yml

e2e        | starting tests
e2e        | ⚙️ setting up TSS address
e2e        | ⏳running - deploy a contract
e2e        | testdapp_zevm deployed at 0x0eEcd709B767bd54CF5Ec5266672dE96F12Ad7D3
e2e        | ✅ completed in 2.725003792s - deploy a contract
e2e        | tests finished successfully in 11.498876042s
e2e        |  ---💰 Total gas spent ---
e2e        | * ZETA spent:  5866042
e2e        |  ---📈 E2E Test Report ---
Name      Success    Time            Spent
deploy    ✅          8.591339833s    ZETA:5866042

Closes: #2227

[skosito]

looks good, just in PR description, contract name and success message seems to mention testdapp_evm in command and testdapp_zevm in message:

zetae2e run deploy:testdapp_evm --config bsc_config.yml

e2e        | starting tests
e2e        | ⚙️ setting up TSS address
e2e        | ⏳running - deploy a contract
e2e        | testdapp_zevm deployed at 0x0eEcd709B767bd54CF5Ec5266672dE96F12Ad7D3

i think its ok to be part of run command, but probably would be cleaner to have separate deploy command like zetae2e deploy, i think some commands like balances are already run in CI?

[lumtis]

looks good, just in PR description, contract name and success message seems to mention testdapp_evm in command and testdapp_zevm in message:

zetae2e run deploy:testdapp_evm --config bsc_config.yml

e2e        | starting tests
e2e        | ⚙️ setting up TSS address
e2e        | ⏳running - deploy a contract
e2e        | testdapp_zevm deployed at 0x0eEcd709B767bd54CF5Ec5266672dE96F12Ad7D3

Copypaste mistake

i think its ok to be part of run command, but probably would be cleaner to have separate deploy command like zetae2e deploy, i think some commands like balances are already run in CI?

Can be change if everyone think this makes sense. For the codebase simplicity, this also makes sense to me to use run as you just need to add a new function in the e2e array.
A new command namespace would need some new logic to execute network interactions that is already available with the current design

[skosito]

looks good, just in PR description, contract name and success message seems to mention testdapp_evm in command and testdapp_zevm in message:

zetae2e run deploy:testdapp_evm --config bsc_config.yml

e2e        | starting tests
e2e        | ⚙️ setting up TSS address
e2e        | ⏳running - deploy a contract
e2e        | testdapp_zevm deployed at 0x0eEcd709B767bd54CF5Ec5266672dE96F12Ad7D3

Copypaste mistake

i think its ok to be part of run command, but probably would be cleaner to have separate deploy command like zetae2e deploy, i think some commands like balances are already run in CI?

Can be change if everyone think this makes sense. For the codebase simplicity, this also makes sense to me to use run as you just need to add a new function in the e2e array. A new command namespace would need some new logic to execute network interactions that is already available with the current design

ah ok i didnt think about that, leaving it in run makes sense then