runtime: add warp-time feature for "fast" runtime

[mnaamani]

Added a "warp-time" cargo feature for use with production runtime configuration to address #4894

To test build and run local chain (with production configration)

WASM_BUILD_TOOLCHAIN=nightly-2022-11-15 cargo build --release --features warp-time

./target/release/joystream-node --chain prod-test --tmp --alice --rpc-cors=all --pruning=archive

┆Issue is synchronized with this Asana task by Unito

[freakstatic]

@mnaamani are you sure you want to have "two names" for the same "feature"?
warp-time vs fast-block-production

[freakstatic]

will not this make testing-runtime with fast-block-production by default?

[mnaamani]

That is already the case. The testing runtime uses 1s blocks (but doesn't warp the timing)

[freakstatic]

oh maybe I misunderstood, so fast-block-production it's the regular testing environment and warp-time is the one with block production of 1s right?

[mnaamani]

oh maybe I misunderstood, so fast-block-production it's the regular testing environment and warp-time is the one with block production of 1s right?

Correct.
Not exactly.

testing-runtime feature and warp-time both enable 1s block times
testing-runtime uses different runtime constants for council/election/proposal periods than production.
warp-time if enabled with production runtime will use the production runtime constants and for periods which are defined using hours!,minutes!,days! macros will not be real minutes,hours,days .. they will be warped times.. so for example hours!(1) will be number of blocks (based on 6s) so 60 * 60 / 6 = 600 blocks. But since a blocks are actually at 1s intervals, that is actually 600 / 60 = 10 (real) minutes.