[5.0] Disable EOS VM OC's subjective compilation limits in unit tests

[linh2931]

When EOS VM OC is used in unit tests, contract actions are not dispatched until EOS VM OC has finished compilation. If a unit test violates EOS VM OC's subjective compilation limits, the unit test will fail. This is most notably problematic for EOS EVM because EOS EVM's exhaustive tests run afoul of OC's subjective limits. Another problem with OC's subjective limits are they prevent ASAN from being used, because ASAN's 16TB of virtual memory usage is flagged by OC's subjective limits.

This PR disables OC subjective limits: cpu limits, vm limits, stack size limit, and generated code size limit in unit tests. It also adds unit tests to make sure limits to work properly.

Resolves #1573

[spoonincode]

The only feedback I'd consider important is moving the libtester configuration in to default_config() if we can, which ought to remove that large if( .. && I believe.

Using an optional and getting rid of soft/hard as part of the config isn't a blocker.

[spoonincode]

I don't really think there is a need for both soft/hard limits here. I can't think of a reason we'd ever set them differently. It also wouldn't be appropriate if we ever ran on Windows.

[spoonincode]

I can't help but feel std::optional would be a better choice for these items. default_config() could be modified to simply .reset() each of them,

leap/libraries/testing/include/eosio/testing/tester.hpp

Lines 400 to 410 in e4df534

	static std::pair<controller::config, genesis_state> default_config(const fc::temp_directory& tempdir, std::optional<uint32_t> genesis_max_inline_action_size = std::optional<uint32_t>{}) {
	controller::config cfg;
	cfg.blocks_dir = tempdir.path() / config::default_blocks_dir_name;
	cfg.state_dir = tempdir.path() / config::default_state_dir_name;
	cfg.state_size = 1024*1024*16;
	cfg.state_guard_size = 0;
	cfg.contracts_console = true;
	cfg.eosvmoc_config.cache_size = 1024*1024*8;
	// don't use auto tier up for tests, since the point is to test diff vms
	cfg.eosvmoc_tierup = chain::wasm_interface::vm_oc_enable::oc_none;

and since that occurs before validating_tester's Lambda conf_edit, eosvmoc_limits_tests can still override them back to however it wants them.

Regardless of optional usage, doing this part in default_config() feels like right spot since that's where other libtester-specific configuration items are set.

An optional should be able to be plumbed through easily, and something like

leap/libraries/chain/webassembly/runtimes/eos-vm-oc/compile_trampoline.cpp

Lines 172 to 174 in e4df534

	if(conf.cpu_limits.rlim_cur != RLIM_INFINITY) {
	setrlimit(RLIMIT_CPU, &conf.cpu_limits);
	}

becomes

if(conf.cpu_limits) {
   struct rlimit cpu_limit = {*conf.cpu_limit, *conf.cpu_limit};
   setrlimit(RLIMIT_CPU, &cpu_limit);
}

[linh2931]

The only feedback I'd consider important is moving the libtester configuration in to default_config() if we can, which ought to remove that large if( .. && I believe.

Using an optional and getting rid of soft/hard as part of the config isn't a blocker.

Thank you Matt @spoonincode for you suggestions! They make code much simpler. I have incorporated them.

[spoonincode]

I think you can remove this FC_REFLECT now

[linh2931]

Thanks. I missed this.