Adding deployment/initialization features via scripts

[DOBEN]

Task description

Adding deplyment/initialization template scripts with some boilerplate code which can be created using cargo-generate command. It would reduce the number of tools a smart contract developer has to interact with (no concordium-client or our hosted frontend needed anymore) to get their protocol deployed on chain.

A new deploy/migrate template folder will be added to Concordium smart contract default template. This folder includes scripts and boilerplate code written in Rust which can be executed to deploy/initialize the smart contracts.

There are two distinguished flows supported to deploy the smart contracts with this template project.

• Automated flow: A given key file and URL to a node allows to run scripts locally and deploy the contracts by signing the transaction with the given key and sending it to the node. The local flow is recommended when developing the protocol actively since it is fully automated and speeds up the testing process on testnet.
• Frontend flow: A local backend server and a local frontend are spun up. The front end pulls periodically for new transaction requests that the backend creates based on the deployment scripts. This new transaction is not signed yet but in the correct format to be forwarded by the front end to the Concordium browser wallet where the transaction is signed and sent to the node that the Concordium browser wallet is connected to. The frontend flow is recommended to get a protocol live on mainnet using hardware wallets.

Sub-tasks

Automated flow:
e.g.

cargo run -- --node http://node.testnet.concordium.com:20000 --account ./3PXwJYYPf6fyVb4GJquxSZU8puxrHfzc4XogdMVot8MUQK53tW.export --modules ./default.wasm.v1 --modules ./default2.wasm.v1