feat: support switch backend binaries by height

[jjyr]

This PR support upgrade backend binaries by height.

Now, instead of define backends in the config.toml we define backend_switch:

pub struct BackendSwitchConfig {
    pub switch_height: u64,
    pub backends: Vec<BackendConfig>,
}

switch_height means in which height we use the new version of backend. For example:

To upgrade godwoken config file, we should move all the backends fields into a backend switch clause such as: BackendSwitchConfig {switch_height: 0, backends}, when we need to upgrade a backend, we define a new backend switch item follows the original one such as: BackendSwitchConfig {switch_height: 1000, backends: <new SUDT backend>}. Then when the tip block arrives the 1000 height, the new SUDT backend will be loaded instead the old one, the other backends are not change.

This change affects the following API:

https://github.com/nervosnetwork/godwoken/blob/develop/docs/RPC.md#method-gw_get_node_info

Consider mostly use-case of this API is to use the validator_script_type_hash field of a backend, I think we can only returns backends at 0 height for now.

[gw-bot]

Running integration test

Workflow Run Id: 2426636431

Components:

• prebuilds: v1.1-202205301006,v1.1
• godwoken: f998684
• scripts: prebuilds 03011e0
• polyjuice: prebuilds 2607851
• kicker: 6d6232c
• tests: 6828c7c

Manually running integration test

Post a comment contains

/itest
[prebuilds: tag]
[godwoken: branch/ref]
[scripts: branch/ref]
[polyjuice: branch/ref]
[web3: branch/ref]
[kicker: branch/ref]
[tests: branch/ref]

Note: [] means optional, for example

/itest
prebuilds: dev-202203280240
godwoken: develop
scripts: 81676d9d53ffdf5bbaa60483928d07da16eb4a88
polyjuice: e37553b9

Run Result

failure

Run Result

failure

[blckngm]

Binary search could be used to improve performance if the number of switches is high.

[jjyr]

Right, but since the chain is keep growing, the later version of backend has more possibility to be selected.