Add a container for a smart contract bundle

[hackaugusto]

The goal is to have a data type to represent the constraint of version compatibility, this can be used to provide better type safety and as a nice way of sharing the necessary data to interact the blockchain.

A bundle for plain smart contracts:

• An typed attribute for each of the smart contracts that is part of the bundle and that together.
• For each of the smart contracts it needs:
  • The abi
  • The contract_version
  • The smart contract bytecode to do the deployment (IMO this should be an special type because it may need linking)
  • The runtimebytecode (IMO this should be an special type because it may need linking)
  • A list of the library dependencies

The bundle for deployed smart contracts:

• The above smart contract definition can be extended/wrapped and have the following added to it:
  • The chain_id
  • The address
  • The gas estimation for each function (IMO this should be a custom class for each smart contract, and not a dictionary)

This is a rough sketch, please further iterate and refine the design.

[hackaugusto]

My motivation for this is that currently:

• The contract manager does not have the chain_id, so the values have to be passed around together
• The contract manager does not have the gas estimation in it, so the path of the smart contract has to be passed around
• The gas estimation is a dictionary, which has led to bugs where the wrong key was used and the type checker cannot catch it.

[pirapira]

Related #1085