feat!: speicfy on-chain parameters explicitly in genesis

[Erigara]

Description

Currently it's not possible to submit genesis which doesn't pass under default parameter values (i.e. large genesis).
This PR fixes that allowing to specify parameters inside genesis.json so that they are applied before processing rest of instructions.

[mversic]

the downside of this approach is that SetParameter instruction will not get validated with the executor specified in the genesis.json

[Erigara]

I see, another downside is that custom parameters is not registered yet.
In this case we can left Upgrade to be first instruction, then we should make sure that set parameters works fine under new executor default parameters.

[mversic]

I see, another downside is that custom parameters is not registered yet.
In this case we can left Upgrade to be first instruction, then we should make sure that set parameters works fine under new executor default parameters.

We can make Upgrade be the first instruction but not check it for executor limits. Then apply parameters and then all other

[Erigara]

I see, another downside is that custom parameters is not registered yet.
In this case we can left Upgrade to be first instruction, then we should make sure that set parameters works fine under new executor default parameters.

We can make Upgrade be the first instruction but not check it for executor limits. Then apply parameters and then all other

Regestring executor itself is not that heavy.
So i don't expect any problems under default parameters.
Executor limits is a problem when we validate transaction with a lot of instructions in it.

[mversic]

Also it's possible to set parameters on executor migration. But I like the simplicity of providing them through genesis.json