Sync calls

[abizjak]

Purpose

Introduce V1 version of smart contracts that supports synchronous calls.

Implements part of #236

Changes

1. Revise module and contract instance type to be versioned by the Wasm module version. The version of the module determines the version of the contract instance. For simplicity and maintainability these are not parametrized by protocol version. The scheduler is the gatekeeper that disallows V1 modules and instances in protocol versions <= 3. This was not possible for PersistentInstance since its BlobStorable implementation did not have sufficient versioning. This is added in protocol versions 4 and up.
2. Introduce V1 contract execution engine bindings and implement handling of V1 contracts in the scheduler.
3. Add an InvokeContract API endpoint and implement invoking a contract at the end of a given block. Implementing this necessitated some minor refactoring of the environment/scheduler abstractions. In particular removing txHash from the TransactionMonad state. It is unclear why that was there.

Depends on

• Introduce v1 version of the host. This host supports synchronous contract calls. concordium-wasm-smart-contracts#24
• Introduce types for parameters and entrypoints. concordium-contracts-common#33
• Sync calls concordium-base#115
• Add invoke contract entrypoint. concordium-grpc-api#7

Checklist

• My code follows the style of this project.
• The code compiles without warnings.
• I have performed a self-review of the changes.
• I have documented my code, in particular the intent of the
  hard-to-understand areas.
• (If necessary) I have updated the CHANGELOG.

[MilkywayPirate]

First leg.

[MilkywayPirate]

Looks good

[Bargsteen]

Great work!

[Bargsteen]

LGTM. 😊