On-demand module compile

[magicxyyz]

Resolves NIT-2633

[eljobe]

I'm afraid I cannot realistically review this with everything going on with BoLD. Sorry. Removing myself as a reviewer for now.

[magicxyyz]

we might need to set moduleActivationMandatory here to true and activate the module each time we need to recompile to get the activationInfo (here info) to check info.moduleHash against moduleHash.

alternatively, we can skip the check if info is nil, so we'd have:

if info != nil && info.moduleHash != moduleHash {
	log.Error("failed to reactivate program", "address", addressForLogging, "expected moduleHash", moduleHash, "got", info.moduleHash)
	return nil, fmt.Errorf("failed to reactivate program. address: %v, expected ModuleHash: %v", addressForLogging, moduleHash)
}

[magicxyyz]

there is also a question how it should work in context of the later code:

currentHoursSince := hoursSinceArbitrum(time)
if currentHoursSince > program.activatedAt {
	// stylus program is active on-chain, and was activated in the past
	// so we store it directly to database
	batch := statedb.Database().WasmStore().NewBatch()
	rawdb.WriteActivation(batch, moduleHash, asmMap)
	if err := batch.Write(); err != nil {
		log.Error("failed writing re-activation to state", "address", addressForLogging, "err", err)
	}
} else {
	// program activated recently, possibly in this eth_call
	// store it to statedb. It will be stored to database if statedb is commited
	statedb.ActivateWasm(info.moduleHash, asmMap)
}

can we just use moduleHash instead of info.moduleHash here?