Add Contract Deployment System

[HDauven]

Summary

We currently only support the deployment of genesis contracts in Rusk. The virtual machine itself contains the logic to deal with deployments. To allow for post-genesis deployments, we need to add a contract deployment system.

Possible solution design or implementation

We need to:

1. Transaction type: Introduce a transaction type or add an extra field to specify it is a contract deployment. This transaction will include the compiled bytecode of the contract. (Related issue Add contract deployment transaction #1882)
2. Contract format: Specify a common contract format in ABI form. (Wiki: Contract Deployment Format, ID format: Implement contract ID generation mechanism #1884)
3. Address generation: Implement a mechanism for generating a unique address for each deployment.
4. Gas and fees: Define the gas cost for deploying a smart contract. (Charge for a contract deployment transaction #1883)
5. Security: Consider whether we need some form of verification procedure to ensure the validity and security of a deployed contract. (Related issue Prevent JIT bomb attacks piecrust#351)
6. Documentation: Provide minimal documentation on the standards/procedures for third-party devs to follow when deploying a contract. (Related issue https://github.com/dusk-network/docs/issues/74, TODO: Add DIP)
7. Tooling: Provide a simple tool to deploy contracts. (Related issue: CLI Tool for smart contracts' deployment dusk-deploy-cli#1)

[HDauven]

Closing, dusk-network/piecrust#351 will be tackled separately.