[feature] Allow different states in wasm::Runtime & link-time checking

[Arjentix]

Initially it's a sub-task for #3230 .

Problems

The problem is that in #3230 I need to introduce another entypoint which should be executed with data different from our current State. For example there will be no account_id, but current desing forces me to use it.

Also with current design we skip link-time checking. We always link all functions. But for example query_triggering_event() function shouldn't be executed from Smart Contract or Validator, it should be executed only from Trigger.

Solution

Make Runtime generic over state it uses. This will allow split current big State into different types and use different Linker's for Runtime to implement link-time checking.

How to test from outside world

When this will be implemented there will be no way to execute inappropriate functions from WASM.

Things that should fail:

1. Executing query_triggering_event() from Smart Contract or Validator
2. Execution query_operation_to_validate() from Smart Contract or Trigger